more edits

hauntsaninja · hauntsaninja · commit 9e5a9988892c · 2020-11-27T16:48:23.000-08:00
diff --git a/docs/source/kinds_of_types.rst b/docs/source/kinds_of_types.rst
@@ -247,8 +247,8 @@ X | Y syntax for Unions
 -----------------------
 
 :pep:`604` introduced an alternative way for spelling union types. In Python
-3.10 and later, it is possible to write ``Union[int, str]`` as ``int | str``. It
-is possible to use this syntax in versions of Python where it isn't supported by
+3.10 and later, you can write ``Union[int, str]`` as ``int | str``. It is
+possible to use this syntax in versions of Python where it isn't supported by
 the runtime with some limitations, see :ref:`runtime_troubles`.
 
 .. code-block:: python
diff --git a/docs/source/runtime_troubles.rst b/docs/source/runtime_troubles.rst
@@ -275,24 +275,25 @@ the built-in collections or those from :py:mod:`collections.abc`
    y: dict[int, str]
    z: Sequence[str] = x
 
+There is limited support for using this syntax in Python 3.7 and later as well.
 If you use ``from __future__ import annotations``, mypy will understand this
-syntax in Python 3.7 and later. However, since this will not be supported by the
-Python interpreter at runtime, make sure you're aware of the caveats mentioned
-in the notes at :ref:`future annotations import<future-annotations>`.
+syntax in annotations. However, since this will not be supported by the Python
+interpreter at runtime, make sure you're aware of the caveats mentioned in the
+notes at :ref:`future annotations import<future-annotations>`.
 
-Using new syntax
-----------------
+Using X | Y syntax for Unions
+-----------------------------
 
 Starting with Python 3.10 (:pep:`604`), you can spell union types as ``x: int |
 str``, instead of ``x: typing.Union[int, str]``.
 
+There is limited support for using this syntax in Python 3.7 and later as well.
 If you use ``from __future__ import annotations``, mypy will understand this
-syntax in Python 3.7 and later. However, since this will not be supported by the
-Python interpreter at runtime (if evaluated, ``int | str`` will raise
-``TypeError: unsupported operand type(s) for |: 'type' and 'type'``), make sure
-you're aware of the caveats mentioned in the notes at :ref:`future annotations
-import<future-annotations>`. You can also use the new syntax in string literal
-types or type comments.
+syntax in annotations, string literal types, type comments and stub files.
+However, since this will not be supported by the Python interpreter at runtime
+(if evaluated, ``int | str`` will raise ``TypeError: unsupported operand type(s)
+for |: 'type' and 'type'``), make sure you're aware of the caveats mentioned in
+the notes at :ref:`future annotations import<future-annotations>`.
 
 Using new additions to the typing module
 ----------------------------------------
