Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 072ab6c

Browse files
committed
More small fixes
1 parent 9c019db commit 072ab6c

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

doc/devel/documenting_mpl.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -106,7 +106,7 @@ An example docstring looks like:
106106
def hlines(self, y, xmin, xmax, colors='k', linestyles='solid',
107107
label='', **kwargs):
108108
"""
109-
Plot horizontal lines at each `y` from `xmin` to `xmax`.
109+
Plot horizontal lines at each *y* from *xmin* to *xmax*.
110110
111111
Parameters
112112
----------
@@ -129,7 +129,7 @@ An example docstring looks like:
129129
130130
Other Parameters
131131
----------------
132-
**kwargs : `~matplotlib.collections.LineCollection` properties.
132+
**kwargs : `~matplotlib.collections.LineCollection` properties.
133133
134134
See also
135135
--------
@@ -244,7 +244,7 @@ Referring to Matplotlib documents
244244
=================================
245245

246246
In the documentation, you may want to include to a document in the
247-
Matplotlib src, e.g., a license file or an image file from `mpl-data`,
247+
Matplotlib sources, e.g., a license file or an image file from `mpl-data`,
248248
refer to it via a relative path from the document where the rst file
249249
resides, e.g., in :file:`users/navigation_toolbar.rst`, you can refer to the
250250
image icons with::
@@ -287,7 +287,7 @@ files are duplicated and large)
287287
Internal section references
288288
===========================
289289

290-
To maximize internal consistency in section labelling and references,
290+
To maximize internal consistency in section labeling and references,
291291
use hyphen separated, descriptive labels for section references, e.g.:
292292

293293
.. code-block:: rst
@@ -300,7 +300,7 @@ and refer to it using the standard reference syntax:
300300
301301
See :ref:`howto-webapp`
302302
303-
Keep in mind that we may want to re-organize the contents later, so
303+
Keep in mind that we may want to reorganize the contents later, so
304304
please try to avoid top level names in references like ``user`` or ``devel``
305305
or ``faq`` unless necessary, because for example the FAQ "what is a
306306
backend?" could later become part of the users guide, so the label:

0 commit comments

Comments
 (0)