diff --git a/docs/docsite/rst/reference_appendices/interpreter_discovery.rst b/docs/docsite/rst/reference_appendices/interpreter_discovery.rst
index 740891ea783..23d1d970929 100644
--- a/docs/docsite/rst/reference_appendices/interpreter_discovery.rst
+++ b/docs/docsite/rst/reference_appendices/interpreter_discovery.rst
@@ -49,5 +49,3 @@ auto_silent
 You can still set ``ansible_python_interpreter`` to a specific path at any
 variable level (for example, in host_vars, in vars files, in playbooks, and so on).
 Setting a specific path completely disables automatic interpreter discovery; Ansible always uses the path specified.
-
-.. seealso:: :ref:`python_3_support` for ``ansible_python_interpreter`` usage examples.
diff --git a/docs/docsite/rst/reference_appendices/python_3_support.rst b/docs/docsite/rst/reference_appendices/python_3_support.rst
index 61239b748c4..5c60a4ea85e 100644
--- a/docs/docsite/rst/reference_appendices/python_3_support.rst
+++ b/docs/docsite/rst/reference_appendices/python_3_support.rst
@@ -1,5 +1,3 @@
-.. _python_3_support:
-
 ================
 Python 3 Support
 ================
@@ -70,12 +68,6 @@ Using Python 3 on the managed machines with commands and playbooks
     $ ansible localhost-py3 -m ping
     $ ansible-playbook sample-playbook.yml
 
-* To use the first Python found on ``PATH`` or if the Python interpreter path is not known in advance, you can use ``/usr/bin/env python`` such as:
-
-.. code-block:: shell
-
-    ansible_python_interpreter="/usr/bin/env python"
-
 
 Note that you can also use the `-e` command line option to manually
 set the python interpreter when you run a command.   This can be useful if you want to test whether