Apply suggestions from code review

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

Author: zklaus

peps/pep-0780.rst

@@ -3,31 +3,34 @@ Title: ABI features as environment markers
 Author: Klaus Zimmermann <klaus_zimmermann@gmx.de>,
         Ralf Gommers <ralf.gommers@gmail.com>
 Sponsor: Lysandros Nikolaou <lisandrosnik@gmail.com>
-Discussions-To: https://discuss.python.org/t/60007
 Status: Draft
 Type: Standards Track
 Topic: Packaging
 Created: 21-Mar-2025
 Python-Version: 3.14
+Post-History:
+  `5 Aug 2024 <https://discuss.python.org/t/60007>`__,
 
 ..
-    If adopted, the contents of this pep should be integrated into the
+    If accepted, the contents of this PEP should be integrated into the
     canonical documentation in the Python Packaging User Guide and the
     following directive should be added here:
     .. canonical-pypa-spec:: :ref:`packaging:dependency-specifiers`
 
 Abstract
 ========
 
-This PEP defines new environment markers for project dependencies.
+This PEP defines using ABI features as environment markers for project
+dependencies, through a new ``sys_abi_features`` environment marker and
+:data:`!sys.abi_features` attribute in the :mod:`sys` module.
 :pep:`508` (later moved to :ref:`packaging:dependency-specifiers`) introduced
 environment markers to specify dependencies based on rules that describe
 when the dependency should be used.
 This PEP extends the environment markers to allow specifying dependencies
 based on specific ABI features of the Python interpreter.
 For this, it defines a set of `ABI Features`_ and specifies how they are made
 available via an `Addition to the Python Standard Library`_ in the form of a
-new attribute ``sys.abi_features``, as well as for `Environment Markers`_ as a
+new attribute :data:`!sys.abi_features`, as well as for `Environment Markers`_ as a
 new marker variable, ``sys_abi_features``.
 
 Motivation
@@ -55,7 +58,7 @@ marker for free-threading`_ Discourse thread:
 - Cython has (experimental) support for free-threading only in its master
   branch, and is used by a lot of projects that already publish ``cp313t``
   wheels. Picking up the wrong Cython version is causing a lot of obscure build
-  failures and runtime crashes. It would be quite beneficial if the metadata
+  failures and runtime crashes. It would be beneficial if the metadata
   could express that (c.f. `Require Cython Pre-release for Free-Threaded
   Python`_).
 - CFFI has no support for free-threading yet, and `Armin Rigo, one of the
@@ -73,23 +76,21 @@ marker for free-threading`_ Discourse thread:
 While these concrete examples may be addressed later this year by Cython and
 CFFI making compatible releases, the same issue is going to repeat further up
 the stack. The free-threading rollout is expected to take several years, and an
-environment marker for free-threading will make that rollout significantly less
-bumpy.
+environment marker for free-threading will make that rollout significantly easier.
 
 Another important ABI feature that is not yet covered by environment markers is
 the bitness of the interpreter. In most cases, the ``sys_platform`` or
 ``platform_system`` markers are enough, because there's only a single bitness
 in use per platform. This is not the case on Windows however: both 32-bit and
 64-bit Python interpreters are widely used on x86-64 Windows. Not being able to
-distinguish between the two may be relevant for packages that provide C
+distinguish between the two may be relevant for packages that provide compiled
 extensions. For example, SciPy does not provide ``win32`` wheels (it isn't able
 to due to the lack of a suitable 32-bit compiler toolchain with Fortran
 support). Those wheels lacking can be awkward especially for projects where
 SciPy is an optional dependency only. In that case, it would be useful to be
 able to specify that SciPy is required *unless* the interpreter is a 32-bit one
-on Windows (c.f. `Require SciPy Unless on 32-bit win32`_) - it avoids users who
-install such packages to get failed from-source installs because of the missing
-wheels.
+on Windows (c.f. `Require SciPy Unless on 32-bit win32`_), to avoid failed
+from-source installations due to the missing wheels.
 
 
 Rationale
@@ -122,7 +123,7 @@ more clarity.
 A Forward Looking View on Free-Threaded Python
 ----------------------------------------------
 
-:pep:`703`, which is the accepted proposal for free threading, states that the
+:pep:`703`, the accepted proposal for free threading, states that the
 rollout of free-threaded Python should be gradual, which has been clarified
 by the Python Steering Council in `the PEP 703 acceptance post`_ to mean a
 three stage process over multiple releases. It is therefore important to make
@@ -193,7 +194,7 @@ ABI features are intrinsic properties of the Python interpreter, expressed as
 simple, understandable strings.
 However, not all features are equally applicable to all Python interpreters or
 Python versions. For example, the distinction between free-threaded and
-GIL-enabled interpreters is only relevant for CPython >=3.13, but the bitness
+GIL-enabled interpreters is only relevant for CPython 3.13 onwards, but the bitness
 of the interpreter is relevant for all interpreters.
 
 All interpreters MUST handle the following ABI features as stated.