diff options
| author | Ned Batchelder <ned@nedbatchelder.com> | 2018-01-21 22:36:18 -0500 |
|---|---|---|
| committer | Ned Batchelder <ned@nedbatchelder.com> | 2018-01-21 22:36:18 -0500 |
| commit | e7a7b13fde81be114a8b6bba9483ba0fbdea729d (patch) | |
| tree | e4155e7599fa67980e93cfba8c6a2fd30f7b3f9b | |
| parent | 96269ab63bcbb0bc7d5520e1dc8226608275889d (diff) | |
| download | python-coveragepy-e7a7b13fde81be114a8b6bba9483ba0fbdea729d.tar.gz | |
Fix typos
| -rw-r--r-- | CHANGES.rst | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/CHANGES.rst b/CHANGES.rst index d6fbd09..08b62e3 100644 --- a/CHANGES.rst +++ b/CHANGES.rst @@ -20,8 +20,8 @@ Unreleased - The ``include`` and ``omit`` options can be specified for both the ``[run]`` and ``[report]`` phases of execution. 4.4.2 introduced some incorrect - interations between those phases, where the options for one were confused for - the other. This is now corrected, fixing `issue 621`_ and `issue 622`_. + interactions between those phases, where the options for one were confused + for the other. This is now corrected, fixing `issue 621`_ and `issue 622`_. Thanks to Daniel Hahler for seeing more clearly than I could. - The ``coverage combine`` command used to always overwrite the data file, even @@ -213,7 +213,7 @@ Version 4.3.2 --- 2017-01-16 - Let's say you ran the HTML report over and over again in the same output directory, with ``--skip-covered``. And imagine due to your heroic - test-writing efforts, a file just acheived the goal of 100% coverage. With + test-writing efforts, a file just achieved the goal of 100% coverage. With coverage.py 4.3, the old HTML file with the less-than-100% coverage would be left behind. This file is now properly deleted. |