bpo-43766: Fix TypeGuard docs (#25660)

1 files changed, 3 insertions, 8 deletions

diff --git a/Doc/library/typing.rst b/Doc/library/typing.rst
index cb9ba45..8b1ce34 100644
--- a/Doc/library/typing.rst
+++ b/Doc/library/typing.rst
@@ -974,10 +974,10 @@ These can be used as types in annotations using ``[]``, each having a unique syn
 
          def func1(val: List[object]):
              if is_str_list(val):
-                 # Type of ``val`` is narrowed to List[str]
+                 # Type of ``val`` is narrowed to ``List[str]``.
                  print(" ".join(val))
              else:
-                 # Type of ``val`` remains as List[object]
+                 # Type of ``val`` remains as ``List[object]``.
                  print("Not a list of strings!")
 
    If ``is_str_list`` is a class or instance method, then the type in
@@ -994,12 +994,7 @@ These can be used as types in annotations using ``[]``, each having a unique syn
       wider form. The main reason is to allow for things like
       narrowing ``List[object]`` to ``List[str]`` even though the latter
       is not a subtype of the former, since ``List`` is invariant.
-      The responsibility of
-      writing type-safe type guards is left to the user.  Even if
-      the type guard function passes type checks, it may still fail at runtime.
-      The type guard function may perform erroneous checks and return wrong
-      booleans.  Consequently, the type it promises in ``TypeGuard[TypeB]`` may
-      not hold.
+      The responsibility of writing type-safe type guards is left to the user.
 
    ``TypeGuard`` also works with type variables.  For more information, see
    :pep:`647` (User-Defined Type Guards).