Reference 'Python' instead of 'Python 3'

doc/man/sphinx-apidoc.rst

@@ -103,12 +103,13 @@ Options
 
 .. option:: --implicit-namespaces
 
-   By default sphinx-apidoc processes sys.path searching for modules only.
+   Without this option, :program:`sphinx-apidoc` searches :data:`sys.path`
-   Python 3.3 introduced :pep:`420` implicit namespaces that allow module path
+   for Python packages containing :file:`__init__.py` files,
-   structures such as ``foo/bar/module.py`` or ``foo/bar/baz/__init__.py``
+   or single-file Python modules.
-   (notice that ``bar`` and ``foo`` are namespaces, not modules).
 
-   Interpret paths recursively according to PEP-0420.
+   This option instead uses :pep:`420` implicit namespaces that allow
+   layouts paths such as ``foo/bar/module.py`` or ``foo/bar/baz/__init__.py``
+   (note that ``bar`` and ``foo`` are namespaces, not modules).
 
 .. option:: -M, --module-first
 

doc/usage/extensions/intersphinx.rst

@@ -222,8 +222,10 @@ Showing all links of an Intersphinx mapping file
 To show all Intersphinx links and their targets of an Intersphinx mapping file,
 run ``python -m sphinx.ext.intersphinx url-or-path``.  This is helpful when
 searching for the root cause of a broken Intersphinx link in a documentation
-project. The following example prints the Intersphinx mapping of the Python 3
+project.
-documentation::
+The following example prints the Intersphinx mapping of the Python documentation:
+
+.. code-block:: console
 
    $ python -m sphinx.ext.intersphinx https://docs.python.org/3/objects.inv
 

doc/usage/extensions/napoleon.rst

@@ -212,7 +212,7 @@ type checkers and IDEs can take advantage of them for static code
 analysis. :pep:`484` was then extended by :pep:`526` which introduced
 a similar way to annotate variables (and attributes).
 
-Google style with Python 3 type annotations:
+Google style with type annotations:
 
 .. code-block:: python