Apply suggestions from code review

Co-authored-by: Kurt McKee <[email protected]>

Author: sirosen

docs/authorization/globus_app/apps.rst

@@ -110,16 +110,16 @@ For example,
     # after the context manager, any storage is implicitly closed
 
 
-However, when token storages are created explicitly, they are not automatically
-closed, and the user becomes responsible for closing them. For example,
+However, when token storage instances are created by the user, they are not automatically
+closed, and the user is responsible for closing them. For example,
 in the following usage, the user must close the token storage:
 
 .. code-block:: python
 
     from globus_sdk import GlobusAppConfig, UserApp
     from globus_sdk.token_storage import SQLiteTokenStorage
 
-    # this manually created storage will not be automatically closed
+    # this token storage is created by the user and will not be closed automatically
     sql_storage = SQLiteTokenStorage("tokens.sqlite")
 
     # create an app configured to use this storage
@@ -131,8 +131,8 @@ in the following usage, the user must close the token storage:
     with UserApp("a-different-app", client_id="OTHER_ID", config=config) as app:
         do_stuff(app)
 
-    # at this stage, the storage will still not be closed
-    # it should be explicitly closed
+    # At this stage, the storage will still be open.
+    # It should be explicitly closed:
     sql_storage.close()
 
 

docs/core/base_client.rst

@@ -49,8 +49,8 @@ For example, in the following usage, the user must close the transport:
         with SearchClient(app=app, transport=my_transport) as client:
             ...  # any usage
 
-    # at this stage, the transport will not be closed
-    # it should be explicitly closed
+    # At this stage, the transport will still be open.
+    # It should be explicitly closed:
     my_transport.close()
 
 

docs/user_guide/getting_started/minimal_script.rst

@@ -99,7 +99,8 @@ One of them is exactly the same as the tutorial steps above, in a single block.
 The next is a version of the tutorial which leverages the context manager
 interfaces of the app and client to do cleanup.
 This is slightly more verbose, but such usage is recommended because it ensures
-resources associated with the client and app are properly closed.
+that network and filesystem resources associated with the client and app are
+properly closed.
 
 The final example includes an explicit login step, so you can control when that
 login flow happens!
@@ -117,7 +118,7 @@ Like the previous example, it uses the context manager style to ensure proper cl
 
     ..  tab-item:: With Context Managers
 
-        This example is the same as the tutorial, but does safer resource cleanup.
+        This example is the same as the tutorial, but safely cleans up resources.
 
         .. literalinclude:: list_groups_improved.py
             :caption: ``list_groups_improved.py`` [:download:`download <list_groups_improved.py>`]