dist-info.files table isn't an open issue

Author: sethmlarson

peps/pep-0770.rst

@@ -156,7 +156,7 @@ To avoid this delay, simplify overall how to include SBOMs, and to give
 flexibility to build backends and tools, this PEP proposes using a subdirectory
 under ``.dist-info`` to safely add data to a Python package while avoiding the
 need for new metadata fields and versions. This mechanism allows build backends
-and tools to begin using the feature described in this PEP immediate after
+and tools to begin using the feature described in this PEP immediately after
 acceptance without the head-of-line blocking on other projects adopting the PEP.
 
 Storing files in the ``.dist-info`` or ``.data`` directory
@@ -530,17 +530,6 @@ Conditional project source SBOM files
 How can a project specify an SBOM file that is conditional? Under what
 circumstances would an SBOM document be conditional?
 
-Statically defining source SBOM files
--------------------------------------
-
-How can SBOM files within a project source (and outside a project source tree)
-be specified statically such that files are added to ``.dist-info/sboms``?
-
-A previous version of this PEP suggested a mechanic for
-adding files into subdirectories under ``.dist-info/`` using a top-level
-``pyproject.toml`` table ``[dist-info.files]``. This addition has been
-refactored out of this PEP and will be proposed in a separate PEP.
-
 References
 ==========