capitalization

Author: warsaw

peps/pep-0694.rst

@@ -164,7 +164,7 @@ these steps:
    as part of the publishing session.
 #. Negotiate the specific :ref:`file upload mechanism <file-upload-mechanisms>` to use
    between client and server.
-#. Execute File Upload Mechanism for the file upload session(s) using the negotiated mechanism(s).
+#. Execute the file upload mechanism for the file upload session(s) using the negotiated mechanism(s).
 #. Complete the file upload session(s), marking them as completed or canceled.
 #. Complete the publishing session, publishing or discarding the stage.
 #. Optionally check the status of a publishing session.
@@ -196,7 +196,7 @@ standard content type that describes what the content is, what version of the AP
 and what serialization format has been used.
 
 This standard request content type applies to all requests *except* for requests to execute
-a File Upload Mechanism, which will be specified by the documentation for that mechanism.
+a file upload mechanism, which will be specified by the documentation for that mechanism.
 
 The structure of the ``Content-Type`` header for all other requests is:
 
@@ -747,17 +747,16 @@ the following keys:
     indicating the current state of the file upload session.
 
 ``expires-at``
-    An :rfc:`3339` formatted timestamp string representing when the server will expire this File Upload
-    Session.  This string **MUST** represent a UTC timestamp using the "Zulu" (i.e. ``Z``) marker,
+    An :rfc:`3339` formatted timestamp string representing when the server will expire this file upload
+    session.  This string **MUST** represent a UTC timestamp using the "Zulu" (i.e. ``Z``) marker,
     and use only whole seconds (i.e. no fractional seconds).  The session **SHOULD** remain active
     until at least this time unless the client cancels or completes it. Servers **MAY** choose to
     extend this expiration time, but should never move it earlier.
 
 ``mechanism``
-    A mapping containing the necessary details for the supported mechanism
-    as negotiated by the client and server.
-    This mapping **MUST** contain a key ``identifier`` which maps to
-    the identifier string for the chosen File Upload Mechanism.
+    A mapping containing the necessary details for the supported mechanism as negotiated by the client and
+    server.  This mapping **MUST** contain a key ``identifier`` which maps to the identifier string for the
+    chosen file upload mechanism.
 
 .. _file-upload-session-links:
 
@@ -911,7 +910,7 @@ File Upload Mechanisms
 Servers **MUST** implement :ref:`required file upload mechanisms <required-file-upload-mechanisms>`.
 Such mechanisms serve as a fallback if no server specific implementations exist.
 
-Each major version of the Upload API **MUST** specify at least one required File Upload Mechanism.
+Each major version of the Upload API **MUST** specify at least one required file upload mechanism.
 
 New required mechanisms **MUST NOT** be added
 and existing required mechanisms **MUST NOT** be removed