Draft: draft-ietf-gnap-core-protocol

Commentary: type , - beit -be it , 
 To edit notification comments on pull requests , go to your . 
 " beit " is n't a word , it should be " be it " . 
 As I was reading through the latest version of the draft , I spotted a typo within section 2.1.1 . It should says accesstoken object , not acccess_token object .
Paragraph (version A):
To request a single access token, the client instance sends an
"acccess_token" object composed of the following fields.
Paragraph (version B):
To request a single access token, the client instance sends an
"access_token" object composed of the following fields.
Paragraph (version A):
During the interaction process, the client instance usually hands
control of the user experience over to another component, beit the
system browser, another application, or some action the resource
owner is instructed to take on another device.  By using an
interaction finish method, the client instance can be securely
notified by the AS when the interaction is completed and the next
phase of the protocol should occur.  This process includes
information that the client instance can use to validate the finish
call from the AS and prevent some injection, session hijacking, and
phishing attacks.
Paragraph (version B):
During the interaction process, the client instance usually hands
control of the user experience over to another component, be it the
system browser, another application, or some action the resource
owner is instructed to take on another device.  By using an
interaction finish method, the client instance can be securely
notified by the AS when the interaction is completed and the next
phase of the protocol should occur.  This process includes
information that the client instance can use to validate the finish
call from the AS and prevent some injection, session hijacking, and
phishing attacks.
Paragraph (version A):
When starting an interactive grant request, a client application has
a number of protocol elements that it needs to manage, including
nonces, references, keys, access tokens, and other elements.  During
the interaction process, the client instance usually hands control of
the user experience over to another component, beit the system
browser, another application, or some action the resource owner is
instructed to take on another device.  In order for the client
instance to make its continuation call, it will need to recall all of
these protocol elements at a future time.  Usually this means the
client instance will need to store these protocol elements in some
retrievable fashion.
Paragraph (version B):
When starting an interactive grant request, a client application has
a number of protocol elements that it needs to manage, including
nonces, references, keys, access tokens, and other elements.  During
the interaction process, the client instance usually hands control of
the user experience over to another component, be it the system
browser, another application, or some action the resource owner is
instructed to take on another device.  In order for the client
instance to make its continuation call, it will need to recall all of
these protocol elements at a future time.  Usually this means the
client instance will need to store these protocol elements in some
retrievable fashion.