Apply suggestions from code review

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>

Author: woodruffw

peps/pep-0792.rst

@@ -1,15 +1,15 @@
 PEP: 792
 Title: Project status markers in the simple index
 Author: William Woodruff <william@yossarian.net>,
-        Facundo Tuesca <facundo.tuesca@trailofbits.com>
+        Facundo Tuesca <facundo.tuesca@trailofbits.com>,
 Sponsor: Donald Stufft <donald@stufft.io>
 PEP-Delegate: Donald Stufft <donald@stufft.io>
-Discussions-To: https://discuss.python.org/t/79356
+Discussions-To: Pending
 Status: Draft
 Type: Standards Track
 Topic: Packaging
 Created: 08-Apr-2025
-Post-History: `03-Feb-2025 <https://discuss.python.org/t/79356/>`__
+Post-History: `03-Feb-2025 <https://discuss.python.org/t/79356/>`__,
 
 Abstract
 ========
@@ -23,9 +23,8 @@ Rationale and Motivation
 
 The "status" of a project is an important piece of metadata, made more important
 by growth in both the breadth and depth of the Python packaging ecosystem.
-Both humans and tools use project statuses (or proxies for status,
-such as recent activity) to determine whether the project is maintained or
-otherwise suitable for consumption.
+Project status (or proxies such as recent activity) is useful to know in
+determining whether a project is maintained or otherwise suitable for consumption.
 
 Python packaging has at least three different mechanisms for communicating
 the "status" of a project:
@@ -55,8 +54,10 @@ the "status" of a project:
    and will render them with a notice when the user navigates directly to them.
 
    Yanking is machine-readable like trove classifiers, but is single-purpose
-   rather than general-purpose: users can specify a free-form "yank reason,"
-   but the semantics of yanking are fixed.
+   rather than general-purpose: users can specify a free-text reason for
+   yanking a given distribution package, but the semantics of yanking are
+   fixed, and no reliable inference of project status can be made by a machine
+   based upon that free-text reason.
 
 3. PyPI itself has *project statuses*, which apply to the entire project
    (i.e., all releases and distributions). Project statuses have both
@@ -66,25 +67,27 @@ the "status" of a project:
      a strengthened yank: the project remains entirely uninstallable while
      quarantined.
 
-   * Project maintainers can "archive" a project. Archiving a project
+   * Project owners can "archive" a project. Archiving a project
      disables new release and distribution uploads to that project,
-     but otherwise has no effect on the project's downloadability.
+     but otherwise has no effect on the ability to download a project.
 
    Project statuses are machine-readable *in principle*, but are not currently
    exposed via any of PyPI's APIs. Instead, PyPI renders project statuses on
-   each project's user-facing (i.e. non-index) HTML.
-
-In summary: there are multiple ways to communicate the "status" of a project in
-Python packaging, but none of these mechanisms are *simultaneously* (1)
-machine-readable, (2) general, (3) index-agnostic, and (4) updatable across
-the entire project (instead of per-release or per-distribution).
-
-.. csv-table::
-    :header: "Mechanism", "Machine-readable?", "General?", "Index-agnostic?", "Project updatable?"
-
-    "Trove classifiers", "✅", "✅", "✅", "❌"
-    "Yanking", "✅", "❌", "✅", "✅"
-    "Project statuses", "✅", "✅", "❌", "✅"
+   each project's user-facing (i.e. non-index) webpage.
+
+In summary, there are multiple ways to communicate the "status" of a project in
+Python packaging. However, none of them satisfy the four characteristics we desire.
+There is no current project status indicator that is machine-readable, general, 
+index-agnostic, and applies to the entire project, instead of per-release or
+per-distribution.
+
+================= ================ ======= ============== ============
+Mechanism         Machine-readable General Index-agnostic Project-wide
+================= ================ ======= ============== ============
+Trove classifiers ✅               ✅      ✅            ❌
+Yanking           ✅               ❌      ✅            ✅
+Project statuses  ✅               ✅      ❌            ✅
+================= ================ ======= ============== ============
 
 This PEP proposes adopting PyPI's project statuses as an index-agnostic
 mechanism, satisfying all four conditions.
@@ -183,7 +186,7 @@ For example, the following would be a valid HTML index response for
 ``sampleproject`` after is has been marked as ``quarantined``:
 
 .. code-block:: html
-    :emphasize-lines: 5
+   :emphasize-lines: 5
 
     <!DOCTYPE html>
     <html>
@@ -215,7 +218,7 @@ For example, the following would be a valid JSON index response for
 ``sampleproject`` after is has been marked as ``quarantined``:
 
 .. code-block:: json
-    :emphasize-lines: 5
+   :emphasize-lines: 5
 
     {
       "meta": {