Fixing some typos

3 files changed, 6 insertions, 6 deletions

diff --git a/docs/oauth2/endpoints/authorization.rst b/docs/oauth2/endpoints/authorization.rst
index 3c42387..9c0cea1 100644
--- a/docs/oauth2/endpoints/authorization.rst
+++ b/docs/oauth2/endpoints/authorization.rst
@@ -58,7 +58,7 @@ Grant and the Client Credentials Grant.
             }
             # these credentials will be needed in the post authorization view and
             # should be persisted between. None of them are secret but take care
-            # to ensure their integrety if embedding them in the form or cookies.
+            # to ensure their integrity if embedding them in the form or cookies.
             from your_datastore import persist_credentials
             persist_credentials(credentials)
 
diff --git a/docs/oauth2/endpoints/endpoints.rst b/docs/oauth2/endpoints/endpoints.rst
index 42b1deb..0e70798 100644
--- a/docs/oauth2/endpoints/endpoints.rst
+++ b/docs/oauth2/endpoints/endpoints.rst
@@ -5,10 +5,10 @@ Endpoints in OAuth 2 are targets with a specific responsibility and often
 associated with a particular URL. Because of this the word endpoint might be
 used interchangably from the endpoint url.
 
-There main three responsibilities in an OAuth 2 flow is to authorize access to a
+The main three responsibilities in an OAuth 2 flow is to authorize access to a
 certain users resources to a client, to supply said client with a token
 embodying this authorization and to verify that the token is valid when the
-client attempts to access thee user resources on their behalf.
+client attempts to access the user resources on their behalf.
 
 .. toctree::
     :maxdepth: 2
diff --git a/docs/oauth2/endpoints/token.rst b/docs/oauth2/endpoints/token.rst
index 9bf9f8d..b01cda6 100644
--- a/docs/oauth2/endpoints/token.rst
+++ b/docs/oauth2/endpoints/token.rst
@@ -3,9 +3,9 @@ Token creation
 ==============
 
 Token endpoints issue tokens to clients who have already been authorized access,
-be it by explicit actions from the user or implicitely. The token response is
-well defined and typically consist of an unguessable access token, the token
-type, its expiration from now in seconds and depending on the scenario, a
+be it by explicit actions from the user or implicitly. The token response is
+well defined and typically consists of an unguessable access token, the token
+type, its expiration from now in seconds, and depending on the scenario, a
 refresh token to be used to fetch new access tokens without authorization.
 
 One argument for OAuth 2 being more scalable than OAuth 1 is that tokens may