PEP 830: Editorial pass on round-2 additions

Break up two adjacent "rather than" pairs (Rationale and sys.monitoring
paragraphs) and reorder/consolidate the Change History bullets so spec
changes lead, followed by Rationale, a single Rejected Ideas bullet, a
single Open Issues bullet, and housekeeping.

Author: gpshead

peps/pep-0830.rst

@@ -232,7 +232,7 @@ The timestamp is recorded when the exception object is created rather than
 when it is raised.  In the overwhelmingly common ``raise SomeError(...)``
 form these are the same moment.  Where they differ, instantiation time is
 generally the more useful value: a bare ``raise`` or ``raise exc`` re-raise
-preserves the time the error first occurred rather than when it was last
+preserves the time the error first occurred, not when it was last
 re-thrown, and code that constructs exceptions, accumulates them, and later
 wraps them in an ``ExceptionGroup`` gets the time each error was detected.
 
@@ -420,7 +420,7 @@ preserves the original timestamp on re-raise.
 This is expected to cost more than the struct-field approach.  ``RAISE``
 fires once per Python frame during unwind rather than once per exception, so
 the callback runs more often than the task requires, and each invocation is
-dispatched through vectorcall rather than called directly.  Without a struct
+dispatched through vectorcall, not called directly.  Without a struct
 field, storing the value allocates the exception's instance ``__dict__``
 plus a ``PyLongObject`` for the timestamp, or for ``add_note()`` the dict
 plus a ``__notes__`` list and formatted string.  One of the limited
@@ -602,32 +602,26 @@ Change History
 
 - 18-Apr-2026
 
-  - Clarified that ``__timestamp_ns__`` is UTC, that clock-read failure
-    yields ``0``, and how free-list and singleton ``MemoryError`` instances
-    are timestamped.
-  - Clarified that ``str(exc)`` and ``repr(exc)`` are unchanged, and that
-    the ``iso`` display format has microsecond resolution.
   - Changed the ``ns`` display format from an integer with an ``ns`` suffix
     to seconds with nine decimal digits, allowing direct use with
     ``datetime.fromtimestamp()``.  Dropped the ``us`` format; ``ns`` is now
-    the default format when the feature is enabled via ``1`` or with no
-    explicit format value.
-  - Added Rejected Ideas entries for returning ``None`` when unset and for
-    using a coarse-resolution clock.
-  - Replaced the ``traceback`` formatting parameter ``no_timestamp`` with a
+    the default when enabled via ``1`` or with no explicit format value.
+  - Replaced the ``traceback`` module ``no_timestamp`` parameter with a
     tri-state ``timestamps`` (default ``None``, follow the global setting).
-  - Noted in Control Flow Exceptions that ``hasattr``, three-argument
-    ``getattr``, and the dict miss paths do not instantiate exceptions in
-    CPython's hot paths and need no special handling.
-  - Added a Rationale subsection on instantiation time vs. raise time, and
-    an Open Issues entry deferring "time of first raise".
-  - Added Rejected Ideas entries for ``sys.excepthook`` and
-    ``sys.monitoring``, with an Open Issues entry on benchmarking the
-    latter.
-  - Reworded the Runtime API rejection.
-  - Added a Rejected Ideas entry for placing the timestamp in the
-    ``Traceback`` header line, and an Open Issues section noting display
-    location is open to revision.
+  - Clarified that ``__timestamp_ns__`` is UTC, that clock-read failure
+    yields ``0``, and how free-list and singleton ``MemoryError`` instances
+    are timestamped; that ``str(exc)`` and ``repr(exc)`` are unchanged; and
+    that the ``iso`` display format has microsecond resolution.
+  - Noted that ``hasattr``, three-argument ``getattr``, and the dict miss
+    paths do not instantiate exceptions in CPython's hot paths and need no
+    special handling.
+  - Added a Rationale subsection on instantiation time vs. raise time.
+  - Added Rejected Ideas entries for ``sys.excepthook``, ``sys.monitoring``,
+    placing the timestamp in the ``Traceback`` header line, returning
+    ``None`` when unset, separate ms/us display formats, and using a
+    coarse-resolution clock; reworded the Runtime API rejection.
+  - Added an Open Issues section covering display location, benchmarking the
+    ``sys.monitoring`` alternative, and recording time of first raise.
   - Made the Motivation example self-contained.