More text corrections

src/web/docusaurus/docs/api-services/auth.md

@@ -12,7 +12,7 @@ SSO service is required for authentication. Telescope doesn't store user informa
 
 _This is what happens step by step in the SSO service:_
 
-- Request to login is sent with the user entering their log in information into Telescope's front end.
+- Logging to the Telescope website will send a login request.
 - Log in data is sent to Seneca's servers.
 - Microsoft SAML-2.
 
@@ -23,15 +23,15 @@ _This is what happens step by step in the SSO service:_
   :::
 
 - Auth cookies are returned to SSO service.
-- SSO service creates a token. A token is basically JSON data.
+- SSO service creates a token, which is basically a JSON data.
 
 ### Tokens
 
 _Token includes information such as:_
 
 1. Who issued it (Us - Telescope server)
-2. Who the audience is (For whom it is made and works for. So, Telescope servers)
-3. Who is the subject of the token (Some ID. In our case, a hashed user email)
+2. Who the audience is (For whom it is made and works for - Telescope servers)
+3. Who is the subject of the token (Some IDs. In our case, a hashed user email)
 4. Claims. Data about the user.
 
 ### Claims
@@ -41,7 +41,7 @@ _Claims include following data:_
 1. Email
 2. First name
 3. Last name
-4. Display name (composite of first and last names)
+4. Display name (consists of first and last names)
 5. Roles
 
 ### Roles