PEP 792: address more feedback

Signed-off-by: William Woodruff <william@yossarian.net>

Author: woodruffw

peps/pep-0792.rst

@@ -22,14 +22,14 @@ 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.
+by growth in both the size and complexity of the Python packaging ecosystem.
 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:
 
-1. Distributions can include *trove classifiers* in their metadata, as
+1. Distribution packages can include *trove classifiers* in their metadata, as
    originally specified in :pep:`301`. The list of supported classifiers is
    `maintained by the PyPA <https://github.com/pypa/trove-classifiers>`_,
    and includes the ``Development Status`` hierarchy. For example, a
@@ -77,17 +77,17 @@ the "status" of a project:
 
 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, 
+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  ✅               ✅      ❌            ✅
-================= ================ ======= ============== ============
+===================== ================ ======= ============== ============
+Mechanism             Machine-readable General Index-agnostic Project-wide
+===================== ================ ======= ============== ============
+Trove classifiers     ✅               ✅       ✅             ❌
+Yanking               ✅               ❌       ✅             ✅
+PyPI project statuses ✅               ✅       ❌             ✅
+===================== ================ ======= ============== ============
 
 This PEP proposes adopting PyPI's project statuses as an index-agnostic
 mechanism, satisfying all four conditions.
@@ -103,7 +103,8 @@ Project status markers
 
 This PEP proposes the following project status markers.
 
-A project **MUST** have exactly one project status marker at any given time.
+A project always has exactly one status. If no status is explicitly noted,
+then the project is considered to be in the ``active`` state.
 
 Indices **MAY** implement any subset of the status markers specified in this
 PEP, as applicable.
@@ -113,7 +114,11 @@ PEP, as applicable.
 
 Description: The project is active. This is the default status for a project.
 
-Index semantics: none.
+Index semantics:
+
+* The index hosting the project **MUST** allow uploads of new distributions to
+  the project.
+* The index **MUST** offer existing distributions of the project for download.
 
 Installer semantics: none.
 
@@ -158,9 +163,7 @@ by another project.
 
 Index semantics:
 
-* The index hosting the project **MUST** allow uploads of new distributions to
-  the project.
-* The index **MUST** offer existing distributions of the project for download.
+* This status shares the same semantics as ``active``.
 
 Installer semantics: