Address @webknjaz's review

source/glossary.rst

@@ -130,14 +130,13 @@ Glossary
         or other resources, or some combination thereof that is intended to be
         packaged into a :term:`Distribution <Distribution Package>`.
 
-        Since most projects create :term:`Distributions <Distribution Package>`
-        using a :term:`build backend` specified in the :ref:`[build-system] table
+        Since projects create :term:`Distributions <Distribution Package>` using
+        a :term:`build backend` specified in the :ref:`[build-system] table
         <pyproject-guide-build-system-table>` of their ``pyproject.toml`` file
-        (or the deprecated practice of having no ``pyproject.toml`` but either
-        ``setup.cfg`` or ``setup.py``), another practical way to define projects
-        currently is something that contains a :term:`pyproject.toml`,
-        :term:`setup.cfg`, or :term:`setup.py` file at the root of the project
-        source directory.
+        (or with the deprecated practice of having a ``setup.py`` without an
+        accompanying ``pyproject.toml``), another practical way to define
+        projects currently is something that contains a :term:`pyproject.toml`
+        or :term:`setup.py` file at the root of the project source directory.
 
         Python projects must have unique names, which are registered on
         :term:`PyPI <Python Package Index (PyPI)>`. Each project will then

source/guides/packaging-namespace-packages.rst

@@ -62,7 +62,7 @@ Creating a namespace package
 There are currently two different approaches to creating namespace packages,
 from which the latter is discouraged:
 
-#. Use `native namespace packages`_. This type of namespace package is defined
+#. Use `native namespace packages`_. This type of namespace package
    is available in Python 3.3 and later. This is recommended if
    packages in your namespace only ever need to support Python 3 and
    installation via ``pip``.
@@ -72,10 +72,11 @@ from which the latter is discouraged:
 Native namespace packages
 -------------------------
 
-Python 3.3 added **implicit** namespace packages. All that is required
-to create a native namespace package is that you just omit
-:file:`__init__.py` from the namespace package directory. An example
-file structure (following :ref:`src-layout <setuptools:src-layout>`):
+Python 3.3 added **implicit** namespace packages (documented in
+:doc:`python:reference/import`). All that is required to create a native
+namespace package is that you just omit :file:`__init__.py` from the
+namespace package directory. An example file structure (following
+:ref:`src-layout <setuptools:src-layout>`):
 
 .. code-block:: text