summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2018-01-10 21:44:28 -0500
committerNed Batchelder <ned@nedbatchelder.com>2018-01-10 21:44:28 -0500
commit6155d7f3f6f658719edd0e418268263c34c5874a (patch)
tree54786ffc4c26b71d11e2062074230c370b4a8192 /doc
parentb7415c4955f43ded43f4a299bc23e8faf171b557 (diff)
downloadpython-coveragepy-6155d7f3f6f658719edd0e418268263c34c5874a.tar.gz
Wrap some lines better.
Diffstat (limited to 'doc')
-rw-r--r--doc/plugins.rst8
1 files changed, 4 insertions, 4 deletions
diff --git a/doc/plugins.rst b/doc/plugins.rst
index fdc1adf..f2bad6d 100644
--- a/doc/plugins.rst
+++ b/doc/plugins.rst
@@ -12,8 +12,8 @@ Plug-ins
.. :history: 20171228T213800, updated for configurer plugins
-Coverage.py's behavior can be extended with third-party plug-ins. A plug-in is a
-separately installed Python class that you register in your .coveragerc.
+Coverage.py's behavior can be extended with third-party plug-ins. A plug-in is
+a separately installed Python class that you register in your .coveragerc.
Plugins can alter a number of aspects of coverage.py's behavior, including
implementing coverage measurement for non-Python files.
@@ -36,8 +36,8 @@ a coverage.py plug-in called ``something.plugin``.
#. Configure coverage.py to use the plug-in. You do this by editing (or
creating) your .coveragerc file, as described in :ref:`config`. The
- ``plugins`` setting indicates your plug-in. It's a list of importable module
- names of plug-ins::
+ ``plugins`` setting indicates your plug-in. It's a list of importable
+ module names of plug-ins::
[run]
plugins =