Tweak ocntent-language wording

--HG--
extra : rebase_source : 6d53b4f2f7aa4e082491f1d9678634ee336507f1

Author: fantasai

css3-text/Overview.html

@@ -471,11 +471,12 @@ <h3 id=terms><span class=secno>1.3. </span> Terminology</h3>
    (human) language the element is declared to be in, according to the rules
    of the <a
    href="http://www.w3.org/TR/CSS21/conform.html#doclanguage">document
-   language</a>. For example, the rules for determining the content language
-   of an HTML element use the <code>lang</code> attribute and are defined in
-   <a href="#HTML5" rel=biblioentry>[HTML5]<!--{{HTML5}}--></a>, and the
-   rules for determining the content language of an XML element use the
-   <code>xml:lang</code> attribute and are <a
+   language</a>. For example, the rules for determining the <a
+   href="#content-language"><i>content language</i></a> of an HTML element
+   use the <code>lang</code> attribute and are defined in <a href="#HTML5"
+   rel=biblioentry>[HTML5]<!--{{HTML5}}--></a>, and the rules for determining
+   the <a href="#content-language"><i>content language</i></a> of an XML
+   element use the <code>xml:lang</code> attribute and are <a
    href="http://www.w3.org/TR/REC-xml/#sec-lang-tag">defined</a> in <a
    href="#XML10" rel=biblioentry>[XML10]<!--{{XML10}}--></a>. Note that it is
    possible for the <a href="#content-language"><i>content language</i></a>
@@ -587,8 +588,8 @@ <h3 id=text-transform><span class=secno>2.1. </span> <a name=caps-prop></a>
    href="#UNICODE" rel=biblioentry>[UNICODE]<!--{{!UNICODE}}--></a>. The UA
    must use the full case mappings for Unicode characters, including any
    conditional casing rules, as defined in Default Case Algorithm section. If
-   (and only if) the content language of the element is, according to the
-   rules of the <a
+   (and only if) the <a href="#content-language"><i>content language</i></a>
+   of the element is, according to the rules of the <a
    href="http://www.w3.org/CSS21/conform.html#doclanguage">document
    language</a>, known, then any appropriate language-specific rules must be
    applied as well. These minimally include, but are not limited to, the
@@ -603,10 +604,10 @@ <h3 id=text-transform><span class=secno>2.1. </span> <a name=caps-prop></a>
     with a different set of mappings to their respective undotted/dotted
     counterparts, which do not exist in English. This mapping must only take
     effect if the <a href="#content-language"><i>content language</i></a> is
-    known to be Turkish (or another Turkic language that uses Turkish casing
-    rules); in other languages, the usual mapping of “I” and “i” is
-    required. This rule is thus conditionally defined in Unicode's
-    SpecialCasing.txt file.
+    Turkish (or another Turkic language that uses Turkish casing rules); in
+    other languages, the usual mapping of “I” and “i” is required.
+    This rule is thus conditionally defined in Unicode's SpecialCasing.txt
+    file.
   </div>
   <!--
     <div class="example">
@@ -1319,8 +1320,8 @@ <h3 id=line-break><span class=secno>5.2. </span> Breaking Rules for
      <li>breaks before the Katakana-Hiragana prolonged sound mark:
       ー U+30FC, ｰ U+FF70
     </ul>
-    If the <a href="#content-language"><i>content language</i></a> is known
-    to be Chinese or Japanese, then additionally:
+    If the <a href="#content-language"><i>content language</i></a> is Chinese
+    or Japanese, then additionally:
     <ul>
      <li>breaks before hyphens:<br>
       ‐ U+2010, – U+2013, 〜 U+301C, ゠ U+30A0
@@ -1337,8 +1338,8 @@ <h3 id=line-break><span class=secno>5.2. </span> Breaking Rules for
      <li>breaks between some inseparable characters:<br>
       ‥ U+2025, … U+2026
     </ul>
-    If the <a href="#content-language"><i>content language</i></a> is known
-    to be Chinese or Japanese, then additionally:
+    If the <a href="#content-language"><i>content language</i></a> is Chinese
+    or Japanese, then additionally:
     <ul>
      <li>breaks before certain centered punctuation marks:<br>
       : U+003A, ; U+003B, ・ U+30FB, ： U+FF1A, ； U+FF1B,

css3-text/Overview.src.html

@@ -203,9 +203,9 @@ <h3 id="terms">
   <p>The <dfn>content language</dfn> of an element is the (human) language
     the element is declared to be in, according to the rules of the
     <a href="http://www.w3.org/TR/CSS21/conform.html#doclanguage">document language</a>.
-    For example, the rules for determining the content language of an HTML
+    For example, the rules for determining the <i>content language</i> of an HTML
     element use the <code>lang</code> attribute and are defined in [[HTML5]],
-     and the rules for determining the content language of an XML element use
+    and the rules for determining the <i>content language</i> of an XML element use
     the <code>xml:lang</code> attribute and are
     <a href="http://www.w3.org/TR/REC-xml/#sec-lang-tag">defined</a> in [[XML10]].
     Note that it is possible for the <i>content language</i> of an element
@@ -298,11 +298,11 @@ <h3 id="text-transform">
       Unicode Standard can be found on the Unicode Consortium Web site
       [[!UNICODE]]. The UA must use the full case mappings for Unicode
       characters, including any conditional casing rules, as defined in
-      Default Case Algorithm section. If (and only if) the content language
+      Default Case Algorithm section. If (and only if) the <i>content language</i>
       of the element is, according to the rules of the
       <a href="http://www.w3.org/CSS21/conform.html#doclanguage">document language</a>,
-      known, then any appropriate language-specific rules must be applied
-      as well.
+      known,
+      then any appropriate language-specific rules must be applied as well.
       These minimally include, but are not limited to, the language-specific
       rules in Unicode's
       <a href="http://www.unicode.org/Public/UNIDATA/SpecialCasing.txt">SpecialCasing.txt</a>.
@@ -314,7 +314,7 @@ <h3 id="text-transform">
         case mappings between &ldquo;I&rdquo; and &ldquo;i&rdquo; are
         replaced with a different set of mappings to their respective
         undotted/dotted counterparts, which do not exist in English. This
-        mapping must only take effect if the <i>content language</i> is known to be Turkish
+        mapping must only take effect if the <i>content language</i> is Turkish
         (or another Turkic language that uses Turkish casing rules);
         in other languages, the usual mapping of &ldquo;I&rdquo;
         and &ldquo;i&rdquo; is required. This rule is thus conditionally
@@ -885,7 +885,7 @@ <h3 id="line-break">
           <li>breaks before the Katakana-Hiragana prolonged sound mark:
             &#x30FC;&nbsp;U+30FC,  &#xFF70&nbsp;U+FF70
         </ul>
-        If the <i>content language</i> is known to be Chinese or Japanese, then additionally:
+        If the <i>content language</i> is Chinese or Japanese, then additionally:
         <ul>
           <li>breaks before hyphens:<br>
             &#x2010;&nbsp;U+2010,  &#x2013;&nbsp;U+2013,  &#x301C;&nbsp;U+301C,
@@ -900,7 +900,7 @@ <h3 id="line-break">
           <li>breaks between some inseparable characters:<br>
             &#x2025;&nbsp;U+2025,  &#x2026;&nbsp;U+2026
         </ul>
-        If the <i>content language</i> is known to be Chinese or Japanese, then additionally:
+        If the <i>content language</i> is Chinese or Japanese, then additionally:
         <ul>
           <li>breaks before certain centered punctuation marks:<br>
             &#x003A;&nbsp;U+003A,  &#x003B;&nbsp;U+003B,  &#x30FB;&nbsp;U+30FB,