Address review

Author: encukou

Doc/c-api/module.rst

@@ -685,7 +685,7 @@ remove it.
    Usually, there is only one variable of this type for each extension module
    defined this way.
 
-   In the :ref:`Stable ABI <stable-abi>` for Free-Threaded Builds (``abi3t``),
+   In the :ref:`Stable ABI <stable-abi>` for free-threaded builds (``abi3t``),
    this struct is opaque, and unusable in practice.
    The struct, including all members, is part of Stable ABI for
    non-free-threaded builds (``abi3``).

Doc/c-api/stable.rst

@@ -68,10 +68,10 @@ versions of Python, without recompilation.
 There are two Stable ABIs:
 
 - ``abi3``, introduced in Pyton 3.2, is compatible with
-  **non**-:term:`free threaded <free-threaded build>` builds of CPython.
+  **non**-:term:`free-threaded <free-threaded build>` builds of CPython.
 
 - ``abi3t``, introduced in Pyton 3.15, is compatible with
-  :term:`free threaded <free-threaded build>` builds of CPython.
+  :term:`free-threaded <free-threaded build>` builds of CPython.
   It has stricter API limitations than ``abi3``.
 
    .. versionadded:: next
@@ -99,8 +99,8 @@ This library only exposes the relevant symbols.
 
 On some platforms, Python will look for and load shared library files named
 with the ``abi3`` or ``abi3t`` tag (for example, ``mymodule.abi3.so``).
-:term:`Free threaded <free-threaded build>` interpreters only recognize the
-``abi3t`` tag, while non-free threaded ones will prefer ``abi3`` but fall back
+:term:`Free-threaded <free-threaded build>` interpreters only recognize the
+``abi3t`` tag, while non-free-threaded ones will prefer ``abi3`` but fall back
 to ``abi3t``.
 Thus, extensions compatible with both ABIs should use the ``abi3t`` tag.
 
@@ -158,13 +158,13 @@ visible to the compiler but should not be used directly.
 .. c:macro:: Py_LIMITED_API
 
    Target ``abi3``, that is,
-   non-:term:`free threaded <free-threaded build>` builds of CPython.
+   non-:term:`free-threaded <free-threaded build>` builds of CPython.
    See :ref:`above <abi3-compiling>` for common information.
 
 .. c:macro:: Py_TARGET_ABI3T
 
    Target ``abi3t``, that is,
-   :term:`free threaded <free-threaded build>` builds of CPython.
+   :term:`free-threaded <free-threaded build>` builds of CPython.
    See :ref:`above <abi3-compiling>` for common information.
 
    .. versionadded:: next
@@ -189,6 +189,8 @@ This means that there are two ways to build for both ``abi3`` and ``abi3t``:
 - define only :c:macro:`!Py_LIMITED_API` and build for free-threaded Python.
 
 
+.. _limited-api-scope-and-performance:
+
 Stable ABI Scope and Performance
 --------------------------------
 
@@ -215,6 +217,8 @@ alongside a version compiled for Stable ABI -- a slower but more compatible
 fallback.
 
 
+.. _limited-api-caveats:
+
 Stable ABI Caveats
 ------------------
 
@@ -224,7 +228,6 @@ Stable ABI prevents *ABI* issues, like linker errors due to missing
 symbols or data corruption due to changes in structure layouts or function
 signatures.
 However, other changes in Python can change the *behavior* of extensions.
-See Python's Backwards Compatibility Policy (:pep:`387`) for details.
 
 One issue that the :c:macro:`Py_TARGET_ABI3T` and :c:macro:`Py_LIMITED_API`
 macros do not guard against is calling a function with arguments that are

Doc/whatsnew/3.15.rst

@@ -390,28 +390,29 @@ agen() for x in a)``.
 C extensions that target the :ref:`Stable ABI <stable-abi>` can now be
 compiled for the new *Stable ABI for Free-Threaded Builds* (also known
 as ``abi3t``), which makes them compatible with
-:term:`free-threaded build <free-threaded build>` builds of CPython.
+:term:`free-threaded <free-threaded build>` builds of CPython.
 This usually requires some non-trivial changes to the source code;
 specifically:
 
 - Switching to API introduced in :pep:`697` (Python 3.12), such as
-  negative :c:member:`~PyType_Spec.basicsize`
+  negative :c:member:`~PyType_Spec.basicsize` and
   :c:func:`PyObject_GetTypeData`, rather than making :c:type:`PyObject`
   part of the instance struct; and
 - Switching from a ``PyInit_`` function to a new export hook,
   :c:func:`PyModExport_* <PyModExport_modulename>`, introduced for this
   purpose in :pep:`793`.
 
-Note that Stable ABI does not offer all functionality CPython has to offer.
+Note that Stable ABI does not offer all the functionality that CPython
+has to offer.
 Extensions that cannot switch to ``abi3t`` should continue to build for
 the existing Stable ABI (``abi3``) and the version-specific ABI for
 free-threading (``cp315t``) separately.
 
 Stable ABI for Free-Threaded Builds should typically
-be selected in a build tool (such as Setuptools, ``meson-python``, Cython,
+be selected in a build tool (such as Setuptools, meson-python, Cython,
 Scikit-build-core, Maturin, and similar).
 At the time of writing this entry, these tools did **not** support ``abi3t``.
-If this is the case for "your" tool, compile for ``cp315t`` separately.
+If this is the case for your tool, compile for ``cp315t`` separately.
 If not using a build tool -- or when writing such a tool -- you can select
 ``abi3t`` by setting the macro :c:macro:`!Py_TARGET_ABI3T` as discussed
 in :ref:`abi3-compiling`.