Review feedback from Carol

Author: zooba

peps/pep-0809.rst

@@ -16,10 +16,12 @@ The Stable ABI as ``abi3`` can no longer be preserved, and requires replacement.
 incompatibilities, with planned retirement after 10 years. A new ABI ``abi2030``
 is planned to provide five years of overlap for the next ABI.
 
-Long-term stability will be enabled without restricting users through a
-mechanism for runtime ABI discovery, allowing extensions to be compiled with
-knowledge of APIs that were not available in prior releases, but can be accessed
-through an identical ABI.
+Long-term stability will be enabled through a mechanism for runtime ABI
+discovery, allowing extensions to be run with earlier releases that support the
+same ABI. Changes and additions during the lifespan of an ABI can be added as
+*interfaces*, allowing them to be discovered at runtime so that callers can
+choose suitable fallback behaviour. Currently, such additions prevent extensions
+from loading at all on earlier runtimes.
 
 The ``abi3`` ABI will be retained in GIL-enabled builds for five years, after
 which time it will be retired (and only ``abi2025`` and ``abi2030`` will be
@@ -38,8 +40,8 @@ Motivation
 ==========
 
 The Stable ABI is currently not available for free-threaded builds.
-Extensions will fail to build when :c:macro:`Py_LIMITED_API` is defined,
-and extensions built for GIL-enabled builds of CPython will fail to load
+Extensions will fail to build when :c:macro:`Py_LIMITED_API` is defined.
+Likewise, extensions built for GIL-enabled builds of CPython will fail to load
 (or crash) on free-threaded builds.
 
 In its `acceptance post <https://discuss.python.org/t/84319/123>`__
@@ -79,13 +81,13 @@ exposes.
 The Limited API is versioned, and building against Limited API 3.X
 yields an extension that is ABI-compatible with CPython 3.X and *any* later
 version (though bugs in CPython sometimes cause incompatibilities in practice).
-Also, the Limited API is not "stable": newer versions may remove API that
-were a part of older versions.
+Also, the Limited API is not "stable": newer versions may remove API items that
+were available in older versions.
 
 This PEP proposes a significant change to versioning of both the Limited API
-and the Stable ABI, with the goal of enabling long-term management of stability
-and compatibility, but without preventing access to innovations for those who
-are using the limited subsets.
+and the Stable ABI. The goal is to enable long-term management of stability
+and compatibility, while also allowing users of the limited subsets to have
+access to innovations in later Python releases.
 
 
 Rationale
@@ -125,10 +127,10 @@ ABI Stability
 
 The Stable ABI will be frozen for a duration of at least 10 years. When a new
 version of the Stable ABI is frozen, the existing version will continue to be
-supported for at least 5 years. This allows ample migration time for consumers
-(that is, package developers) to migrate their entire range of supported
-releases simultaneously. However, if the core team sees no reason to replace the
-current Stable ABI, the new version may be deferred.
+supported for at least 5 years. This allows ample migration time for package
+maintainers (and other users) to migrate their entire range of supported
+releases simultaneously. However, if the Python team sees no reason to replace
+the current Stable ABI, the new version may be deferred.
 
 When a Stable ABI is frozen, the year becomes the name of the ABI. For example,
 we anticipate that the first ABI under this scheme will be ``abi2026``, and will
@@ -163,7 +165,7 @@ New Export Hook (PEP 793)
 -------------------------
 
 Implementation of this PEP requires :pep:`793` (``PyModExport``:
-A new entry  point for C extension modules) to be
+A new entry point for C extension modules) to be
 accepted, providing a new “export hook” for defining extension modules.
 Using the new hook will become mandatory in Limited API 3.15.