PEP 678: Update proposal with .add_note() and acknowledgements section

pep-0678.rst

@@ -121,7 +121,7 @@ Non-goals
 ---------
 Tracking multiple notes as a tuple, rather than by concatenating strings when
 notes are added, is intended to maintain the distinction between the
-individual notes. This might be required in specialized use cases, such 
+individual notes. This might be required in specialized use cases, such
 as translation of the notes by packages like ``friendly-traceback``.
 
 However, ``__notes__`` is *not* intended to carry structured data.  If your
@@ -133,15 +133,15 @@ instead (or additionally) choosing a convention for an attribute, e.g.
 As a rule of thumb, we suggest that you should prefer `exception chaining
 <https://docs.python.org/3/tutorial/errors.html#exception-chaining>`__ when the
 error is going to be re-raised or handled as an individual error, and prefer
-``.add_note()`` when you are collecting multiple exception objects to handle
-together or later. [1]_
+``.add_note()`` when you do not know or wish to change the exception type or
+are collecting multiple exception objects to handle together. [1]_
 
 
 Specification
 =============
 
-``BaseException`` gains a new read-only field ``__notes__``, an initially empty
-tuple, and a new method ``.add_note(note: str | None, *, replace:
+``BaseException`` gains a new read-only attribute ``__notes__``, an initially
+empty tuple, and a new method ``.add_note(note: str | None, *, replace:
 bool=False)``. If ``note`` is not ``None``, it is added to the exception's
 notes which appear in the standard traceback after the exception string. If
 ``replace`` is true, all previously existing notes are removed before the new
@@ -165,8 +165,9 @@ subject to breakage without warning
 <https://docs.python.org/3/reference/lexical_analysis.html#reserved-classes-of-identifiers>`__.
 We are also unaware of any code which *would* be broken by adding ``__notes__``.
 
-While ``add_note()`` is a fairly common method name, our Google and GitHub
-searches did not find any exception classes which define such a method.
+While ``add_note()`` is a fairly common method name, our Google and `GitHub
+searches <https://grep.app/search?q=.add_note%28&filter[lang][0]=Python>`__
+did not find any exception classes which define such a method.
 
 
 How to Teach This
@@ -202,8 +203,8 @@ or merely significant difficulties working out which explanation corresponds to
 which error. The new ``ExceptionGroup`` type intensifies these existing
 challenges.
 
-Keeping the ``__notes__`` attached to the exception object, like the
-traceback, eliminates these problems.
+Keeping the ``__notes__`` attached to the exception object, in the same way as
+the ``__traceback__`` attribute, eliminates these problems.
 
 
 ``raise Wrapper(explanation) from err``