summaryrefslogtreecommitdiff
path: root/doc/tutorial.rst
diff options
context:
space:
mode:
authorGeorg Brandl <georg@python.org>2010-04-17 10:39:51 +0200
committerGeorg Brandl <georg@python.org>2010-04-17 10:39:51 +0200
commit22ac79e1af541e66b002ba35f1cd902a91cceb88 (patch)
tree65279525ae9619d532d21ee67d6bc8c5b9727d38 /doc/tutorial.rst
parentea85d7fb1fdad1fbac214c2653daf388738c3935 (diff)
downloadsphinx-22ac79e1af541e66b002ba35f1cd902a91cceb88.tar.gz
Use the new rst domain in the sphinx docs.
Diffstat (limited to 'doc/tutorial.rst')
-rw-r--r--doc/tutorial.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/tutorial.rst b/doc/tutorial.rst
index bb4116ba..fa6ee2ab 100644
--- a/doc/tutorial.rst
+++ b/doc/tutorial.rst
@@ -90,7 +90,7 @@ Adding content
In Sphinx source files, you can use most features of standard reStructuredText.
There are also several features added by Sphinx. For example, you can add
cross-file references in a portable way (which works for all output types) using
-the :role:`ref` role.
+the :rst:role:`ref` role.
For an example, if you are viewing the HTML version you can look at the source
for this document -- use the "Show Source" link in the sidebar.
@@ -164,7 +164,7 @@ prefix the markup with the domain name::
does the same job if you keep the default setting for the default domain.
There are several more directives for documenting other types of Python objects,
-for example :dir:`py:class` or :dir:`py:method`. There is also a
+for example :rst:dir:`py:class` or :rst:dir:`py:method`. There is also a
cross-referencing :dfn:`role` for each of these object types. This markup will
create a link to the documentation of ``enumerate()``::