Fix a couple of typos

specification/dartLangSpec.tex

@@ -21846,15 +21846,15 @@ \subsubsection{Meta-Variables}
 }
 
 \LMHash{}%
-In this section we use the following meta-variables:
+In this section (\ref{subtypes}) we use the following meta-variables,
+possibly with an index like $X_1$ or $S_j$:
 
 \begin{itemize}
 \item $X$ ranges over type variables.
 \item $C$ ranges over classes,
 \item $F$ ranges over type aliases.
-\item $T$ and $S$ range over types, possibly with an index like $T_1$ or $S_j$.
-\item $B$ ranges over types, again possibly with an index;
-  it is only used as a type variable bound.
+\item $T$ and $S$ range over types.
+\item $B$ ranges over types; it is only used as a type variable bound.
 \item $r$ and $r'$ range over \REQUIRED{} or empty;
   it is used to enable the specification of a named parameter
   which may or may not have the modifier \REQUIRED.
@@ -22077,8 +22077,8 @@ \subsubsection{Informal Subtype Rule Descriptions}
 For example, rule~\SrnRightFutureOrA{} says that
 ``The type $S$ is a \ldots{} of \code{FutureOr<$T$>} \ldots'',
 and this is taken to mean that for any arbitrary types $S$ and $T$,
-showing that $S$ is a subtype of $T$ is sufficient to show that $S$ is
-a subtype of \code{FutureOr<$T$>}.
+in order to show that $S$ is a subtype of \code{FutureOr<$T$>}
+it is sufficient to show that $S$ is a subtype of $T$.
 
 Another example is the wording in rule~\SrnReflexivity{}:
 ``\ldots{} in any environment $\Delta$'',
@@ -22105,7 +22105,7 @@ \subsubsection{Informal Subtype Rule Descriptions}
   Note that this implies that these types are equivalent
   according to the subtype relation.
   We denote these types,
-  and others with the same property (such as \code{FutureOr<Object>}),
+  and others with the same property (such as \code{FutureOr<Object>?}),
   as top types
   (\ref{superBoundedTypes}).
 \Item{\SrnLeftTop}{Left Top}