fixit

Author: iritkatriel

peps/pep-0765.rst

@@ -53,8 +53,8 @@ flag them as a problem.
 Rationale
 =========
 
-A recent `analysis of real world code
-<https://github.com/iritkatriel/finally/blob/main/README.md>`__ shows that:
+A recent
+`analysis of real world code <https://github.com/iritkatriel/finally/blob/main/README.md>`__ shows that:
 
 - These features are rare (2 per million LOC in the top 8,000 PyPI
   packages, 4 per million LOC in a random selection of packages).
@@ -64,13 +64,13 @@ A recent `analysis of real world code
 - Code owners are typically receptive to fixing the bugs, and
   find that easy to do.
 
-See `the appendix<#appendix>`__ for more details.
+See `the appendix <#appendix>`__ for more details.
 
 This new data indicates that it would benefit Python's users if
 Python itself moved them away from this harmful feature.
 
-One of the arguments brought up in `the PEP 601 discussion
-<https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/24>`__
+One of the arguments brought up in
+`the PEP 601 discussion <https://discuss.python.org/t/pep-601-forbid-return-break-continue-breaking-out-of-finally/2239/24>`__
 was that language features should be orthogonal, and combine without
 context-based restrictions. However, in the meantime :pep:`654` has
 been implemented, and it forbids ``return``, ``break`` and ``continue``
@@ -151,8 +151,7 @@ How to Teach This
 
 The change will be documented in the language spec and in the
 What's New documentation. The ``SyntaxWarning`` will alert users
-that their code needs to change. The `empirical evidence
-<https://github.com/iritkatriel/finally/blob/main/README.md>`__
+that their code needs to change. The `empirical evidence <#appendix>`__
 shows that the changes necessary are typically quite
 straightforward.