summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2016-02-22 21:27:46 -0500
committerNed Batchelder <ned@nedbatchelder.com>2016-02-22 21:27:46 -0500
commit85192a6e7d133c053945516d75040cc2295dc014 (patch)
treecc6e5b14931775e859099b18f1b7135fe99cab27
parent165e28cc060fa030c2cd68036ec96a0cf7dcb2f1 (diff)
downloadpython-coveragepy-git-85192a6e7d133c053945516d75040cc2295dc014.tar.gz
Tweak the docs
-rw-r--r--doc/cmd.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/cmd.rst b/doc/cmd.rst
index a66df82d..5f3cc539 100644
--- a/doc/cmd.rst
+++ b/doc/cmd.rst
@@ -113,7 +113,7 @@ Give it a value of ``greenlet``, ``eventlet``, or ``gevent``.
By default, coverage.py does not measure code installed with the Python
interpreter, for example, the standard library. If you want to measure that
-code as well as your own, add the ``-L`` flag.
+code as well as your own, add the ``-L`` (or ``--pylib``) flag.
If your coverage results seem to be overlooking code that you know has been
executed, try running coverage.py again with the ``--timid`` flag. This uses a
@@ -168,7 +168,7 @@ Coverage.py collects execution data in a file called ".coverage". If need be,
you can set a new file name with the COVERAGE_FILE environment variable. This
can include a path to another directory.
-By default,each run of your program starts with an empty data set. If you need
+By default, each run of your program starts with an empty data set. If you need
to run your program multiple times to get complete data (for example, because
you need to supply disjoint options), you can accumulate data across runs with
the ``-a`` flag on the **run** command.