Fix some awkwardness in wording when considering @language in Expansion (from @pchampin).

Author: gkellogg

index.html

@@ -2141,12 +2141,12 @@ <h3>Algorithm</h3>
                 <li>If <var>expanded property</var> is <code>@language</code> and
                   <var>value</var> is not a <a>string</a>, an
                   <a data-link-for="JsonLdErrorCode">invalid language-tagged string</a>
-                  error has been detected and processing is aborted.
-                  <span class="changed">If <var>value</var> is not <a>well-formed</a> according to
-                    <a data-cite="BCP47#section-2.2.9">section 2.2.9</a> of [[BCP47]],
-                    processors SHOULD issue a warning.</span>
+                  error has been detected and processing is aborted,
                   <span class="changed">
-                    Otherwise, set <var>expanded value</var> to <var>value</var>.
+                    otherwise, set <var>expanded value</var> to <var>value</var>.
+                    If <var>value</var> is not <a>well-formed</a> according to
+                    <a data-cite="BCP47#section-2.2.9">section 2.2.9</a> of [[BCP47]],
+                    processors SHOULD issue a warning.
                     When the {{JsonLdOptions/frameExpansion}} flag is set, <var>value</var>
                     may also be an empty <a>map</a> or an array of zero or
                     <a>strings</a>. <var>expanded value</var> will be an