Apply suggestions from code review

Co-authored-by: Adam Turner <9087854+AA-Turner@users.noreply.github.com>

Author: ZeroIntensity

peps/pep-0788.rst

@@ -96,7 +96,7 @@ the thread:
 
 Unfortunately, this isn't correct, because of time-of-call to time-of-use
 issues; the interpreter might not be finalizing during the call to
-:c:func:`Py_IsFinalizing`, but it might start finalizing right after, which
+:c:func:`Py_IsFinalizing`, but it might start finalizing immediately afterwards, which
 would cause the attachment of a thread state (typically via
 :c:func:`PyGILState_Ensure`) to hang the thread.
 
@@ -155,14 +155,14 @@ The existing APIs are broken and misleading
 -------------------------------------------
 
 There are currently two public ways for a user to create and attach their own
-:term:`thread state`; manual use of :c:func:`PyThreadState_New` / :c:func:`PyThreadState_Swap`,
-and :c:func:`PyGILState_Ensure`. The former, :c:func:`PyGILState_Ensure`,
+:term:`thread state`; manual use of :c:func:`PyThreadState_New` & :c:func:`PyThreadState_Swap`,
+and :c:func:`PyGILState_Ensure`. The latter, :c:func:`PyGILState_Ensure`,
 is `significantly more common <https://grep.app/search?q=pygilstate_ensure>`_.
 
 :c:func:`PyGILState_Ensure` generally crashes during finalization
 *****************************************************************
 
-As of this PEP, the current behavior of :c:func:`PyGILState_Ensure` does not
+At the time of writing, the current behavior of :c:func:`PyGILState_Ensure` does not
 match the documentation. Instead of hanging the thread during finalization
 as previously noted, it's extremely common for it to crash with a segmentation
 fault. This is a `known issue <https://github.com/python/cpython/issues/124619>`_