Clarify packaging specifications titles and terminology

source/guides/dropping-older-python-versions.rst

@@ -98,7 +98,7 @@ If using the :ref:`setuptools` build backend, consult the `dependency-management
 Within a Python source package (the zip or the tar-gz file you download) is a text file called PKG-INFO.
 
 This file is generated by the :term:`build backend <Build Backend>` when it generates the source package.
-The file contains a set of keys and values, the list of keys is part of the PyPA standard metadata format.
+The file contains a set of keys and values defined by the :ref:`Core Metadata specification <core-metadata>`.
 
 You can see the contents of the generated file like this:
 

source/index.rst

@@ -15,7 +15,7 @@ Python Packaging User Guide
    tutorials/index
    guides/index
    discussions/index
-   specifications/index
+   Specifications <specifications/index>
    key_projects
    glossary
    support

source/specifications/entry-points.rst

@@ -18,8 +18,8 @@ example:
 
 The entry point file format was originally developed to allow packages built
 with setuptools to provide integration point metadata that would be read at
-runtime with :py:mod:`importlib.metadata`. It is now defined as a PyPA interoperability
-specification in order to allow build tools other than ``setuptools`` to publish
+runtime with :py:mod:`importlib.metadata`. It is now defined as a Python packaging
+interoperability specification in order to allow build tools other than ``setuptools`` to publish
 :py:mod:`importlib.metadata` compatible entry point metadata, and runtime libraries other
 than :py:mod:`importlib.metadata` to portably read published entry point metadata
 (potentially with different caching and conflict resolution strategies).

source/specifications/glob-patterns.rst

@@ -2,7 +2,7 @@
 ``glob`` patterns
 =================
 
-Some PyPA specifications, e.g. :ref:`pyproject.toml's license-files
+Some Python packaging specifications, e.g. :ref:`pyproject.toml's license-files
 <pyproject-toml-license-files>`, accept certain types of *glob patterns*
 to match a given string containing wildcards and character ranges against
 files and directories. This specification defines which patterns are acceptable
@@ -12,7 +12,7 @@ and how they should be handled.
 Valid glob patterns
 ===================
 
-For PyPA purposes, a *valid glob pattern* MUST be a string matched against
+For this specification, a *valid glob pattern* MUST be a string matched against
 filesystem entries as specified below:
 
 - Alphanumeric characters, spaces (`` ``), underscores (``_``), hyphens (``-``),

source/specifications/index.rst

@@ -1,12 +1,15 @@
+.. legacy title, keep for now to avoid breaking incoming links
+.. _pypa-specifications:
+
 .. _`packaging-specifications`:
 
-PyPA specifications
-###################
+Python Packaging Specifications
+###############################
 
 This is a list of currently active interoperability specifications maintained
-by the Python Packaging Authority. The process for updating these standards,
-and for proposing new ones, is documented on
-`pypa.io <https://www.pypa.io/en/latest/specifications/>`__.
+by the Python Packaging Council. The process for updating these standards,
+and for proposing new ones, is documented in
+`the python/packaging-council repo <https://github.com/python/packaging-council#process-for-packaging-standards>`__.
 
 .. toctree::
    :titlesonly:

source/specifications/schemas/index.rst

@@ -1,8 +1,14 @@
+.. legacy title, keep for now to avoid breaking incoming links
+
+.. _pypa-schemas:
+.. _json-schemas:
 .. _`packaging-schemas`:
 
-PyPA schemas
+JSON Schemas
 ############
 
+JSON schemas for data structures defined by the packaging specifications.
+
 - `direct_url.json <direct-url.schema.json>`_
 - `build-details.json <build-details-v1.0.schema.json>`_
 - `pylock.toml <pylock.schema.json>`_