apply more review comments

Author: RonnyPfannschmidt

doc/en/backwards-compatibility.rst

@@ -30,15 +30,15 @@ c) true breakage: should only to be considered when normal transition is unreaso
 
    Examples for such upcoming changes:
 
-   * removal of ``pytest_runtest_protocol/nextitem``
+   * removal of ``pytest_runtest_protocol/nextitem`` - `#895`_
    * rearranging of the node tree to include ``FunctionDefinition``
-   * rearranging of ``SetupState``
+   * rearranging of ``SetupState`` `#895`_
 
    True breakages must be announced first in an issue containing:
 
    * Detailed description of the change
    * Rationale
-   * Expected impact on users and plugin authors
+   * Expected impact on users and plugin authors (example in `#895`_)
 
    After there's no hard *-1* on the issue it should be followed up by an initial proof-of-concept Pull Request.
 
@@ -56,7 +56,7 @@ History
 
 
 Focus primary on smooth transition - stance (pre 6.0)
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 
 Keeping backwards compatibility has a very high priority in the pytest project. Although we have deprecated functionality over the years, most of it is still supported. All deprecations in pytest were done because simpler or more efficient ways of accomplishing the same tasks have emerged, making the old way of doing things unnecessary.
 
@@ -75,3 +75,6 @@ Deprecation Roadmap
 Features currently deprecated and removed in previous releases can be found in :ref:`deprecations`.
 
 We track future deprecation and removal of features using milestones and the `deprecation <https://github.com/pytest-dev/pytest/issues?q=label%3A%22type%3A+deprecation%22>`_ and `removal <https://github.com/pytest-dev/pytest/labels/type%3A%20removal>`_ labels on GitHub.
+
+
+.. _`#895`: https://github.com/pytest-dev/pytest/issues/895