update based on the feedback from the discussion

Author: methane

peps/pep-0781.rst

@@ -2,12 +2,12 @@ PEP: 781
 Title: Adding __type_checking__ constant
 Author: Inada Naoki <songofacandy@gmail.com>
 Discussions-To: https://discuss.python.org/t/85728
-Post-History: 11-Jan-2025 https://discuss.python.org/t/76766
 Status: Draft
 Type: Standards Track
 Topic: Typing
 Created: 24-Mar-2025
 Python-Version: 3.14
+Post-History: `11-Jan-2025 <https://discuss.python.org/t/76766>`__
 
 
 Abstract
@@ -66,15 +66,19 @@ a matching pattern.
 Similar to :data:`typing.TYPE_CHECKING`, type checking tools should treat
 ``__type_checking__`` as ``True``.
 
+Once this PEP is accepted, ``__type_checking__`` will be the preferred way over
+``typing.TYPE_CHECKING``. However, ``typing.TYPE_CHECKING`` will not be deprecated.
+Instead, it will be implemented using ``__type_checking__``, allowing future type
+checkers to focus on handling ``__type_checking__`` only.
+
 
 How to Teach This
 =================
 
-Add this note to the ``typing.TYPE_CHECKING`` document:
-
-> If you don't want to import ``typing``, you can use ``__type_checking__``.
-> Workarounds like ``TYPE_CHECKING = False`` or
-> ``if False:  # TYPE_CHECKING`` are not recommended since Python 3.14.
+* Use ``__type_checking__`` for skipping type-checking code at runtime.
+* Use :data:`typing.TYPE_CHECKING` to support Python versions before 3.14.
+* Workarounds like ``TYPE_CHECKING = False`` or ``if False:  # TYPE_CHECKING``
+  are not recommended since Python 3.14.
 
 
 Reference Implementation