Apply suggestions from code review

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

Author: 3 people

peps/pep-0781.rst

@@ -1,5 +1,5 @@
 PEP: 781
-Title: Make ``TYPE_CHECKING`` builtin
+Title: Make ``TYPE_CHECKING`` a built-in constant
 Author: Inada Naoki <songofacandy@gmail.com>
 Discussions-To: https://discuss.python.org/t/85728
 Status: Draft
@@ -14,11 +14,11 @@ Post-History: `11-Jan-2025 <https://discuss.python.org/t/76766>`__,
 Abstract
 ========
 
-This PEP proposes adding a new builtin, :data:`!TYPE_CHECKING`, to improve
+This PEP proposes adding a new built-in variable, :data:`!TYPE_CHECKING`, to improve
 the experience of writing Python code with type annotations. It is evaluated
 as ``True`` when the code is being analyzed by a static type checker, and as
 ``False`` during normal runtime execution. Unlike :data:`typing.TYPE_CHECKING`,
-which this keyword replaces, it does not require an import statement.
+which this variable replaces, it does not require an import statement.
 
 
 Motivation
@@ -29,7 +29,7 @@ widespread adoption. A challenge with fully-annotated code is that many
 more imports are required in order to bring the relevant name into scope,
 potentially causing import cycles without careful design. This has been
 recognized by :pep:`563` and later :pep:`649`, which introduce two different
-mechanisms for deferred evaluation of type annotations. As :pep:`563` notes,
+mechanisms for deferred evaluation of type annotations. As PEP 563 notes,
 "type hints are ... not computationally free". The :data:`typing.TYPE_CHECKING`
 constant was thus introduced__, initially to aid in breaking cyclic imports.
 
@@ -75,13 +75,13 @@ Since ``TYPE_CHECKING`` doesn't prohibit assignment, existing code using
 
 .. code-block:: python
 
-   # These code will work as before
+   # This code will continue to work
    TYPE_CHECKING = False
    from typing import TYPE_CHECKING
 
 
-User can remove the assingment to ``TYPE_CHECKING`` after they stop using
-Python before 3.14.
+User can remove the assignment to ``TYPE_CHECKING`` after they stop using
+Python 3.13 or older versions.
 
 
 How to Teach This
@@ -90,7 +90,7 @@ How to Teach This
 * Use ``if TYPE_CHECKING:`` for skipping type-checking code at runtime.
 * Use ``from typing import TYPE_CHECKING`` to support Python versions before 3.14.
 * Workarounds like ``TYPE_CHECKING = False`` or ``if False:  # TYPE_CHECKING``
-  are continued to work, but not recommended.
+  will continue to work, but are not recommended.
 
 
 Reference Implementation
@@ -102,7 +102,7 @@ Reference Implementation
 Rejected Ideas
 ==============
 
-Eliminate type-checking-only Code
+Eliminate type-checking-only code
 ---------------------------------
 
 It is considered to add real constant named ``__type_checking__``