summaryrefslogtreecommitdiff
path: root/doc/tutorial
diff options
context:
space:
mode:
Diffstat (limited to 'doc/tutorial')
-rw-r--r--doc/tutorial/automatic-doc-generation.rst2
-rw-r--r--doc/tutorial/describing-code.rst3
2 files changed, 2 insertions, 3 deletions
diff --git a/doc/tutorial/automatic-doc-generation.rst b/doc/tutorial/automatic-doc-generation.rst
index 409bc43d6..ead741780 100644
--- a/doc/tutorial/automatic-doc-generation.rst
+++ b/doc/tutorial/automatic-doc-generation.rst
@@ -9,7 +9,7 @@ docstrings <https://www.python.org/dev/peps/pep-0257/#what-is-a-docstring>`_
in the documentation, rather than having to write the information in two
places.
-Fortunately, :doc:`autodoc </usage/extensions/autodoc>` provides this
+Fortunately, :doc:`the autodoc extension </usage/extensions/autodoc>` provides this
functionality.
Reusing signatures and docstrings with autodoc
diff --git a/doc/tutorial/describing-code.rst b/doc/tutorial/describing-code.rst
index f5c5391ff..f353f9af1 100644
--- a/doc/tutorial/describing-code.rst
+++ b/doc/tutorial/describing-code.rst
@@ -11,8 +11,7 @@ Documenting Python objects
--------------------------
Sphinx offers several roles and directives to document Python objects,
-all grouped together in the Python
-:doc:`domain </usage/restructuredtext/domains>`. For example, you can
+all grouped together in :ref:`the Python domain <python-domain>`. For example, you can
use the :rst:dir:`py:function` directive to document a Python function,
as follows: