Minor text changes

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

@@ -6,13 +6,13 @@ sidebar_position: 5
 
 ## Summary
 
-SSO service is required for authentication. Telescope doesn't store user information itself, we just send it to Seneca's SSO. From that interaction, Telescope creates a token that will only work for a limited amount of time. The token is used in authenticating in various Telescope services, without a need to make requests to Seneca's servers every time. The same token system is also used throughout our Supabase back end.
+SSO service is required for authentication. Telescope doesn't store user information itself, we just send it to Seneca's SSO. From that interaction, Telescope creates a token that will only work for a limited amount of time. The token is used to authenticate various Telescope services without sending requests to Seneca's server every time. The same token system is also used throughout our Supabase backend.
 
 ## Stages
 
 _This is what happens step by step in the SSO service:_
 
-- Request to log in is sent with the user entering their log in information into Telescope's front end.
+- Request to login is sent with the user entering their log in information into Telescope's front end.
 - Log in data is sent to Seneca's servers.
 - Microsoft SAML-2.