mirror of
https://github.com/sphinx-doc/sphinx.git
synced 2025-02-25 18:55:22 -06:00
corrected contractions
This commit is contained in:
@@ -952,7 +952,7 @@ the `Dublin Core metadata <http://dublincore.org/>`_.
|
||||
.. confval:: epub_tocdup
|
||||
|
||||
This flag determines if a toc entry is inserted again at the beginning of
|
||||
it's nested toc listing. This allows easier navigation to the top of
|
||||
its nested toc listing. This allows easier navigation to the top of
|
||||
a chapter, but can be confusing because it mixes entries of different
|
||||
depth in one list. The default value is ``True``.
|
||||
|
||||
|
||||
@@ -24,7 +24,7 @@ Cross-referencing syntax
|
||||
|
||||
Cross-references are generated by many semantic interpreted text roles.
|
||||
Basically, you only need to write ``:role:`target```, and a link will be created
|
||||
to the item named *target* of the type indicated by *role*. The links's text
|
||||
to the item named *target* of the type indicated by *role*. The link's text
|
||||
will be the same as *target*.
|
||||
|
||||
There are some additional facilities, however, that make cross-referencing roles
|
||||
|
||||
@@ -200,7 +200,7 @@ Earlier we mentioned that the :file:`conf.py` file controls how Sphinx processes
|
||||
your documents. In that file, which is executed as a Python source file, you
|
||||
assign configuration values. For advanced users: since it is executed by
|
||||
Sphinx, you can do non-trivial tasks in it, like extending :data:`sys.path` or
|
||||
importing a module to find out the version your are documenting.
|
||||
importing a module to find out the version you are documenting.
|
||||
|
||||
The config values that you probably want to change are already put into the
|
||||
:file:`conf.py` by :program:`sphinx-quickstart` and initially commented out
|
||||
|
||||
@@ -45,7 +45,7 @@ by creating a :class:`~.WebSupport` object for your application::
|
||||
search='xapian')
|
||||
|
||||
You'll only need one of these for each set of documentation you will be working
|
||||
with. You can then call it's :meth:`~.WebSupport.get_document` method to access
|
||||
with. You can then call its :meth:`~.WebSupport.get_document` method to access
|
||||
individual documents::
|
||||
|
||||
contents = support.get_document('contents')
|
||||
|
||||
Reference in New Issue
Block a user