Apply suggestions from code review

Co-authored-by: Hugo van Kemenade <1324225+hugovk@users.noreply.github.com>

Author: methane

peps/pep-0781.rst

@@ -13,7 +13,7 @@ Abstract
 ========
 
 This PEP proposes adding a new keyword ``__type_checking__`` that serves the
-same purpose as ``typing.TYPE_CHECKING``.
+same purpose as :data:`typing.TYPE_CHECKING`.
 This constant is ``True`` when the code is being analyzed by a static type
 checker, and ``False`` during normal runtime execution.
 
@@ -43,8 +43,8 @@ Specification
 It can be used in the same way as ``False``, except it can not be used as
 a matching pattern.
 
-Similar to typing.TYPE_CHECKING, type checking tools should treat
-``__type_checking__`` as True.
+Similar to :data:`typing.TYPE_CHECKING`, type checking tools should treat
+``__type_checking__`` as ``True``.
 
 
 Rationale
@@ -69,15 +69,14 @@ 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__``.
-> Workaround like ``TYPE_CHECKING = False`` or
+> Workarounds like ``TYPE_CHECKING = False`` or
 > ``if False:  # TYPE_CHECKING`` are not recommended since Python 3.14.
 
 
-Resources
-=========
+Reference Implementation
+========================
 
-* Previous discussion: https://discuss.python.org/t/76766
-* Reference Implementation: https://github.com/python/cpython/pull/131641
+* `python/cpython#131641 <https://github.com/python/cpython/pull/131641>`__
 
 
 Copyright