Clarify API stability of PyTypeObject in relation to static types. (GH-96217)

Fixes:
https://github.com/python/cpython/issues/95300

Related:
https://github.com/python/cpython/issues/91271
(cherry picked from commit caa2a9799a47294441e4206037620322eea9ed06)

Co-authored-by: ov2k <ov2k.github@gmail.com>

diff --git a/Doc/c-api/typeobj.rst b/Doc/c-api/typeobj.rst
index 8d7a2ed75fc9ef529cc33e6b22b0c4c9bac0be06..9bb0e6dbbcf87dd389680f061f68b476b6a66698 100644 (file)
--- a/Doc/c-api/typeobj.rst
+++ b/Doc/c-api/typeobj.rst
@@ -2047,9 +2047,9 @@ This results in types that are limited relative to types defined in Python:
   :ref:`sub-interpreters <sub-interpreter-support>`, so they should not
   include any subinterpreter-specific state.
 
-Also, since :c:type:`PyTypeObject` is not part of the :ref:`stable ABI <stable>`,
-any extension modules using static types must be compiled for a specific
-Python minor version.
+Also, since :c:type:`PyTypeObject` is only part of the :ref:`Limited API
+<stable>` as an opaque struct, any extension modules using static types must be
+compiled for a specific Python minor version.
 
 
 .. _heap-types: