Apply suggestions from code review

Co-authored-by: Barry Warsaw <barry@python.org>

Author: ewdurbin

peps/pep-0694.rst

@@ -17,7 +17,7 @@ Abstract
 This PEP proposes an extensible API for uploading files to a Python package index such as PyPI.
 Along with standardization, the upload API provides additional useful features such as support for:
 
-* an publishing session, which can be used to simultaneously publish
+* a publishing session, which can be used to simultaneously publish
   all wheels in a package release;
 
 * "staging" a release, which can be used to test uploads before publicly publishing them,
@@ -620,7 +620,7 @@ Besides the standard ``meta`` key, the request JSON has the following additional
     This mechanism **SHOULD** be chosen from the list of mechanisms advertised in the
     :ref:`Publishing Session response body <publishing-session-response>`.
     A client **MAY** send a mechanism that is not advertised in cases where server operators have
-    documented a new or up-coming mechanism that is available for use on a "pre-release" basis.
+    documented a new or upcoming mechanism that is available for use on a "pre-release" basis.
 
 ``metadata`` (**optional**)
     If given, this is a string value containing the file's `core metadata
@@ -684,7 +684,7 @@ the following keys:
     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 File Upload Mechanism.
+    the identifier string for the chosen File Upload Mechanism.
 
 .. _file-upload-session-links:
 
@@ -747,7 +747,7 @@ A client can cancel an in-progress File Upload Session, or delete a file that ha
 completely uploaded.  In both cases, the client performs this by issuing a ``DELETE`` request to
 the File Upload Session URL of the file they want to delete.
 
-A successful deletion request **MUST** response with a ``204 No Content``.
+A successful deletion request **MUST** respond with a ``204 No Content``.
 
 Once canceled or deleted, a client **MUST NOT** assume that
 the previous File Upload Session resource
@@ -841,11 +841,11 @@ The ``stage`` URL can be passed to installers such as ``pip`` by setting the `--
 <https://pip.pypa.io/en/stable/cli/pip_install/#cmdoption-extra-index-url>`__ flag to this value.
 Multiple stages can even be previewed by repeating this flag with multiple values.
 
-In either case, the index will return views that expose the staged releases to the installer tool,
+If supported, the index will return views that expose the staged releases to the installer tool,
 making them available to download and install into virtual environments built for that last-mile
-testing.  The former option allows for existing installers to preview staged releases with no
-changes, although perhaps in a less user-friendly way.  The latter option can be a better user
-experience, but the details of this are left to installer tool maintainers.
+testing.  This option allows existing installers to preview staged releases with no
+changes to the installer tool required.
+The details of this user experience are left to installer tool maintainers.
 
 
 .. _file-upload-mechanisms:
@@ -870,6 +870,8 @@ Required File Upload Mechanisms
 ``http-post-bytes``
 +++++++++++++++++++
 
+Upload API version 2.0 compliant servers **MUST** support the ``http-post-bytes`` mechanism.
+
 A client executes this mechanism by submitting a ``POST`` request to the ``file_url``
 returned in the ``http-post-bytes`` map of the ``mechanism`` map of the
 :ref:`File Upload Session creation response body <file-upload-session-response>` like:
@@ -930,7 +932,7 @@ File Upload Mechanism string           Server Operator   Mechanism description
 ``vnd-madscience-quantumentanglement`` Mad Science Labs  Upload via quantum entanglement
 ====================================== ================  =========================================================================
 
-If a server intends to match the behavior of another server's implementation, it **MAY** respond
+If a server intends to precisely match the behavior of another server's implementation, it **MAY** respond
 with that implementation's file upload mechanism name.