Address review comments

Author: sethmlarson

peps/pep-0770.rst

@@ -383,12 +383,15 @@ For projects that do contain other software components, documentation will be
 added to the Python Packaging User Guide for how to specify and maintain
 SBOM documents for Python packages in source code.
 
-There are two "camps" of projects that contain other software, those from
-a "packaging ecosystem" (PyPI, Linux distros, Rust, NPM, etc) and those from
+There are two groups of projects that contain other software, those from
+a "packaging ecosystem" (PyPI, Linux distros, Crates.io, NPM, etc) and those from
 outside a packaging ecosystem (vendored C, C++, Fortran). Software that is
 a part of a packaging ecosystem is much easier to identify meaning
 that package maintainers may have their package SBOM data annotated
-automatically by common build tools (auditwheel, cibuildwheel, multibuild, etc).
+automatically by common build tools (
+`auditwheel <https://pypi.org/project/auditwheel>`__,
+`cibuildwheel <https://github.com/pypa/cibuildwheel>`__,
+`multibuild <https://github.com/multi-build/multibuild>`__, etc).
 
 For projects that cannot be automatically annotated, the approach will be to
 generate SBOM files by some means and then include those files manually using