Original text:
could be calling the AS just to get direct user information and have no need to get an access token to call an RS.  (A) The end user interacts with the client instance to indicate a need for resources on behalf of the RO.  This could identify the RS the client instance needs to call, the resources needed, or the and never call an RS, just as it is possible for there not to be a user involved in the delegation process. <del> 1.5.1. </del>  In this example flow, the client instance is a web application that wants access to resources on behalf of the current user, who acts as An example set of protocol messages for this method can be found in example-auth-code. <del> 1.5.2. </del>  In this example flow, the client instance is a device that is capable of presenting a short, human-readable code to the user and directing An example set of protocol messages for this method can be found in example-device. <del> 1.5.3. </del>  In this example flow, the end user and RO roles are fulfilled by different parties, and the RO does not interact with the client An example set of protocol messages for this method can be found in example-async. <del> 1.5.4. </del>  In this example flow, the AS policy allows the client instance to make a call on its own behalf, without the need for an RO to be An example set of protocol messages for this method can be found in example-no-user. <del> 1.5.5. </del>  In this example flow, the client instance receives an access token to access a resource server through some valid GNAP process.  The client token management information, which the client instance will store in place of the values returned in (2). <del> 1.5.6. </del>  In this scenario, the client instance does not call an RS and does not request an access token.  Instead, the client instance only

Reviewer comments:
Deploy Preview for gnap-core-protocol-editors-draft ready! Explore the source changes: a48ba2e1204e2294f34f8550971f65f684ea7992 Inspect the deploy log: Browse the preview:
Sec. 1.5 (Sequences) would be clearer if we named the top sequence - all other sequences have been named. Maybe "main authorization flow"?
The sequences have not been names per say, they just happen to be related to a subtitle. We could of course create a new subsection, but the idea was to place this sequence above the others.
This is purely editorial. Naming it would make it easier to refer to this sequence.

Revised text:
could be calling the AS just to get direct user information and have no need to get an access token to call an RS. <ins> 1.5.1. The following diagram provides a general overview of GNAP, including many different optional phases and connections.  The diagrams in the following sections provide views of GNAP under more specific circumstances. </ins> (A) The end user interacts with the client instance to indicate a need for resources on behalf of the RO.  This could identify the RS the client instance needs to call, the resources needed, or the and never call an RS, just as it is possible for there not to be a user involved in the delegation process.  <ins> 1.5.2. </ins> In this example flow, the client instance is a web application that wants access to resources on behalf of the current user, who acts as An example set of protocol messages for this method can be found in example-auth-code.  <ins> 1.5.3. </ins> In this example flow, the client instance is a device that is capable of presenting a short, human-readable code to the user and directing An example set of protocol messages for this method can be found in example-device.  <ins> 1.5.4. </ins> In this example flow, the end user and RO roles are fulfilled by different parties, and the RO does not interact with the client An example set of protocol messages for this method can be found in example-async.  <ins> 1.5.5. </ins> In this example flow, the AS policy allows the client instance to make a call on its own behalf, without the need for an RO to be An example set of protocol messages for this method can be found in example-no-user.  <ins> 1.5.6. </ins> In this example flow, the client instance receives an access token to access a resource server through some valid GNAP process.  The client token management information, which the client instance will store in place of the values returned in (2).  <ins> 1.5.7. </ins> In this scenario, the client instance does not call an RS and does not request an access token.  Instead, the client instance only