Wrap long lines in RST files

Also wrap longish lines where that helps readability.

Suggested-by: doc8

Author: pabs3

CHANGES.rst

@@ -13,8 +13,10 @@ Changelog
 Features
 ++++++++
 
-- Allow to use a ``str`` as condition for ``@pytest.mark.flaky(condition)``
-  which gets evaluated dynamically similarly to ``@pytest.mark.skipif(condition)``.
+- Allow to use a ``str`` as condition for
+  ``@pytest.mark.flaky(condition)``
+  which gets evaluated dynamically similarly to
+  ``@pytest.mark.skipif(condition)``.
   (`#162 <https://github.com/pytest-dev/pytest-rerunfailures/pull/162>`_
   provided by `@15klli <https://github.com/15klli>`_)
 
@@ -199,11 +201,11 @@ Bug fixes
 4.2 (2018-10-04)
 ----------------
 
-- Fixed #64 issue related to ``setup_class`` and ``fixture`` executions on rerun (Thanks to
-  `@OlegKuzovkov`_ for the PR).
+- Fixed #64 issue related to ``setup_class`` and ``fixture`` executions on
+  rerun (Thanks to `@OlegKuzovkov`_ for the PR).
 
-- Added new ``execution_count`` attribute to reflect the number of test case executions according to #67 issue.
-  (Thanks to `@OlegKuzovkov`_ for the PR).
+- Added new ``execution_count`` attribute to reflect the number of test case
+  executions according to #67 issue. (Thanks to `@OlegKuzovkov`_ for the PR).
 
 .. _@OlegKuzovkov: https://github.com/OlegKuzovkov
 

CONTRIBUTING.rst

@@ -2,8 +2,8 @@
 Contribution getting started
 ============================
 
-Contributions are highly welcomed and appreciated. Every little bit of help counts,
-so do not hesitate!
+Contributions are highly welcomed and appreciated.
+Every little bit of help counts, so do not hesitate!
 
 .. contents::
    :depth: 2
@@ -37,4 +37,5 @@ Preparing Pull Requests
 
 #. Follow **PEP-8** for naming and `black <https://github.com/psf/black>`_ for formatting.
 
-#. Add a line item to the current **unreleased** version in ``CHANGES.rst``, unless the change is trivial.
+#. Add a line item to the current **unreleased** version in ``CHANGES.rst``,
+   unless the change is trivial.

README.rst

@@ -59,15 +59,15 @@ Re-run all failures matching certain expressions
 ------------------------------------------------
 
 To re-run only those failures that match a certain list of expressions, use the
-``--only-rerun`` flag and pass it a regular expression. For example, the following would
-only rerun those errors that match ``AssertionError``:
+``--only-rerun`` flag and pass it a regular expression. For example,
+the following would only rerun those errors that match ``AssertionError``:
 
 .. code-block:: bash
 
    $ pytest --reruns 5 --only-rerun AssertionError
 
-Passing the flag multiple times accumulates the arguments, so the following would only rerun
-those errors that match ``AssertionError`` or ``ValueError``:
+Passing the flag multiple times accumulates the arguments, so the following
+would only rerun those errors that match ``AssertionError`` or ``ValueError``:
 
 .. code-block:: bash
 
@@ -166,7 +166,8 @@ Resources
 Development
 -----------
 
-* Test execution count can be retrieved from the ``execution_count`` attribute in test ``item``'s object. Example:
+* Test execution count can be retrieved from the ``execution_count`` attribute
+  in test ``item``'s object. Example:
 
   .. code-block:: python