Glossary: Improve gradual form and gradual type definitions

Author: bswck

docs/spec/glossary.rst

@@ -65,19 +65,19 @@ This section defines a few terms that may be used elsewhere in the specification
       primary gradual form is :ref:`Any`. The ellipsis (``...``) is a gradual
       form in some, but not all, contexts. It is a gradual form when used in a
       :ref:`Callable` type, and when used in ``tuple[Any, ...]`` (but not in
-      other :ref:`tuple <tuples>` types).
+      other :ref:`tuple <tuples>` types). Types that contain gradual forms do not participate
+      in the :term:`subtype` relation, but they do participate in
+      :term:`consistency <consistent>` and :term:`assignability <assignable>`.
+      They can be :term:`materialized <materialize>` to a more static, or fully static,
+      type. See :ref:`type-system-concepts`.
 
    gradual type
       All types in the Python type system are "gradual". A gradual type may be
       a :term:`fully static type`, or it may be :ref:`Any`, or a type that
       contains ``Any`` or another :term:`gradual form`. A gradual type does not
       necessarily represent a single set of possible runtime values; instead it
       can represent a set of possible static types (a set of possible sets of
-      possible runtime values). Gradual types do not participate in the
-      :term:`subtype` relation, but they do participate in :term:`consistency
-      <consistent>` and :term:`assignability <assignable>`. They can be
-      :term:`materialized <materialize>` to a more static, or fully static,
-      type. See :ref:`type-system-concepts`.
+      possible runtime values).
 
    inline
       Inline type annotations are annotations that are included in the