A few clarifications based on early reviews

Author: warsaw

.github/CODEOWNERS

@@ -702,6 +702,7 @@ peps/pep-0825.rst  @warsaw @dstufft
 peps/pep-0826.rst  @savannahostrowski
 peps/pep-0827.rst  @1st1
 peps/pep-0828.rst  @ZeroIntensity
+peps/pep-0829.rst  @warsaw
 # ...
 peps/pep-2026.rst  @hugovk
 # ...

peps/pep-0829.rst

@@ -94,10 +94,14 @@ File Naming and Discovery
   ``<package>.site.toml``, just like the current ``.pth`` file
   convention.
 
-* The naming convention is ``<package>.site.toml``.  The ``.site``
-  marker distinguishes these from other TOML files that might exist in
-  site-packages and describes the file's purpose (processed by
-  ``site.py``).
+* The file naming format is ``<package>.site.toml``.  The ``.site`` marker
+  distinguishes these from other TOML files that might exist in site-packages
+  and describes the file's purpose (processed by ``site.py``).
+
+* The ``<package>`` prefix should match the package name, but just
+  like with ``.pth`` files, the interpreter does not enforce this.
+  Build backends and installers :ref:`**MAY** <tool-authors>` impose
+  stricter constraints if they so choose.
 
 * ``<package>.site.toml`` files live in the same site-packages directories
   where ``<package>.pth`` files are found today.
@@ -162,9 +166,6 @@ are optional:
 
     [metadata]
     schema_version = 1
-    package = "foo"
-    version = "2.3.4"
-    author = "A Person <aperson@example.com>"
 
     [paths]
     dirs = ["../lib", "/opt/mylib", "{sitedir}/extra"]
@@ -176,12 +177,8 @@ are optional:
 The ``[metadata]`` section
 ''''''''''''''''''''''''''
 
-This section contains package and/or file metadata.  There are no required
-keys, and no semantics are assigned to any keys in this section *except* for
-the optional ``schema_version`` key (see below).  Any additional keys are
-permitted and preserved.
-
-Defined keys:
+This section contains package and/or file metadata.  The only defined key is
+the the optional ``schema_version`` key.
 
 ``schema_version`` (integer, recommended)
     The TOML file schema version number.  Must be the integer ``1``
@@ -193,19 +190,8 @@ Defined keys:
     ``schema_version`` is omitted, the file is processed on a
     best-effort basis with no forward-compatibility guarantees.
 
-Recommended keys:
-
-``package`` (string)
-    The package name.
-
-``version`` (string)
-    The package version.
-
-``author`` (string)
-    The package author.  Should be
-    ``email.utils.parseaddr()``-compatible, e.g.,
-    ``"A person <aperson@example.com>"`` or
-    ``"aperson@example.com"``.
+Additional keys are permitted and preserved, although they are ignored for the
+purposes of this PEP.
 
 
 The ``[paths]`` section
@@ -247,9 +233,10 @@ Directories that do not exist on the filesystem are silently skipped, matching
 The ``[entrypoints]`` section
 '''''''''''''''''''''''''''''
 
-``init`` -- a list of strings specifying entry point references to
-execute at startup.  Each item uses the standard Python entry point
-syntax: ``package.module:callable``.
+``init`` -- a list of strings specifying `entry point
+<https://packaging.python.org/en/latest/specifications/entry-points/>`_
+references to execute at startup.  Each item uses the standard Python
+entry point syntax: ``package.module:callable``.
 
 * The ``:callable`` portion is optional.  If omitted (e.g.,
   ``package.module``), the module is imported via
@@ -448,16 +435,23 @@ migration.  If both exist for the same package, only the
 ``<package>.site.toml`` is processed.  Thus it is recommended that
 packages compatible with older Pythons ship both files.
 
+.. _tool-authors:
 
-For tool authors
-----------------
+For tool makers
+---------------
 
 Build backends and installers should generate ``<package>.site.toml``
 files alongside or instead of ``<package>.pth`` files, depending on
 the package's Python support matrix.  The TOML format is easy to
 generate programmatically using ``tomllib`` (for reading) or string
 formatting (for writing, since the schema is simple).
 
+Build backends **SHOULD** ensure that the ``<package>`` prefix matches
+the package name.
+
+Installers **MAY** validate or enforce that the ``<package>`` prefix
+matches the package name.
+
 
 Reference Implementation
 =========================