address review

Author: blink1073

source/auth/auth.rst

@@ -1113,20 +1113,20 @@ MUST obtain the ``access_key``, ``secret_key`` and ``security_token`` which will
 Caching Credentials
 ___________________
 Credentials fetched by the driver using AWS endpoints MUST be cached and reused
-to avoid hitting AWS rate limitations.  AWS recommends using a suitable
-Software Development Kit (SDK) for your langauge.  If that SDK supports
+to avoid hitting AWS rate limitations. AWS recommends using a suitable
+Software Development Kit (SDK) for your langauge. If that SDK supports
 credential fetch and automatic refresh/caching, then that mechanism can
 be used in lieu of manual caching.
 
 If using manual caching, the "Expiration" field MUST be stored
-and used to determine when to clear the cache.  Credentials are considered
+and used to determine when to clear the cache. Credentials are considered
 valid if they are more than five minutes away from expiring, to the reduce the
 chance of expiration before they are validated by the server.
 
 If there are no current valid cached credentials, the driver MUST initiate a
-credential request.  To avoid adding a bottleneck that would override the
+credential request. To avoid adding a bottleneck that would override the
 ``maxConnecting`` setting, the driver MUST not place a lock on making a
-request.  The cache MUST be written atomically.
+request.  he cache MUST be written atomically.
 
 If AWS authentication fails for any reason, the cache MUST be cleared.