Apply suggestions from code review

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

Author: iritkatriel

peps/pep-0765.rst

@@ -185,7 +185,7 @@ Once downloaded, a
 was used to construct an AST for each file, and traverse it to identify ``break``,
 ``continue`` and ``return`` statements which are directly inside a ``finally`` block.
 
-I then found the current source code for each occurence, and categorized it. For
+I then found the current source code for each occurrence, and categorized it. For
 cases where the code seems incorrect, I created an issue in the project's bug
 tracker. The responses to these issues are also part of the data collected in
 this investigation.
@@ -257,13 +257,12 @@ Here the intention seems to be to return ``NotImplemented`` when an exception is
 raised, but the ``return`` in the ``finally`` block would override the one in the
 ``except`` block.
 
-> [!NOTE]
-> Following the
-> `discussion <https://discuss.python.org/t/an-analysis-of-return-in-finally-in-the-wild/70633/15>`__,
-> I repeated the analysis on a random selection of PyPI packages (to
-> analyze code written by *average* programmers). The sample contained
-> in total 77,398,892 lines of code with 316 instances of ``return``/``break``/``continue``
-> in ``finally``. So about 4 instances per million lines of code.
+.. note:: Following the
+   `discussion <https://discuss.python.org/t/an-analysis-of-return-in-finally-in-the-wild/70633/15>`__,
+   I repeated the analysis on a random selection of PyPI packages (to
+   analyze code written by *average* programmers). The sample contained
+   in total 77,398,892 lines of code with 316 instances of ``return``/``break``/``continue``
+   in ``finally``. So about 4 instances per million lines of code.
 
 **Author reactions**
 
@@ -275,7 +274,7 @@ authors to the problems. Within two weeks, 40 of the 73 issues received a reacti
 from the code maintainers:
 
 - 15 issues had a PR opened to fix the problem.
-- 20 received reactions acknowleding the problem as one worth looking into.
+- 20 received reactions acknowledging the problem as one worth looking into.
 - 3 replied that the code is no longer maintained so this won't be fixed.
 - 2 closed the issue as "works as intended", one said that they intend to
   swallow all exceptions, but the other seemed unaware of the distinction