[css3-fonts] editorial fixups in font feature resolution

Author: John Daggett

css-fonts/Fonts.html

@@ -112,15 +112,15 @@
 
    <h1>CSS Fonts Module Level 3</h1>
 
-   <h2 class="no-num no-toc" id=editors-draft-5-june-2013>Editor's Draft 5
+   <h2 class="no-num no-toc" id=editors-draft-6-june-2013>Editor's Draft 6
     June 2013</h2>
 
    <dl id=authors>
     <dt>This version:
 
     <dd><a
      href="http://dev.w3.org/csswg/css-fonts/">http://dev.w3.org/csswg/css-fonts/</a>
-     <!-- <dd><a href="http://www.w3.org/TR/2013/ED-css3-fonts-20130605/">http://www.w3.org/TR/2013/ED-css3-fonts-20130605/</a> -->
+     <!-- <dd><a href="http://www.w3.org/TR/2013/ED-css3-fonts-20130606/">http://www.w3.org/TR/2013/ED-css3-fonts-20130606/</a> -->
 
 
     <dt>Latest version:
@@ -2665,9 +2665,8 @@ <h3 id=unicode-range-desc><span class=secno>4.5 </span>Character range: the
    correspond to <a href="http://www.unicode.org/charts/">Unicode character
    codepoints</a>. Valid Unicode codepoint values vary between 0 and 10FFFF
    inclusive. Digit values of codepoints are ASCII case-insensitive. For
-   interval ranges, the start and end codepoints must be valid Unicode values
-   and the end codepoint must be greater than or equal to the start
-   codepoint.
+   interval ranges, the start and end codepoints are valid Unicode values and
+   the end codepoint is greater than or equal to the start codepoint.
 
   <p>Wildcard ranges specified with ‘?’ that lack an initial digit (e.g.
    "U+???") are valid and equivalent to a wildcard range with an initial zero
@@ -2971,8 +2970,10 @@ <h3 id=font-face-loading><span class=secno>4.8 </span>Font loading
    <a href="#at-font-face-rule"><code>@font-face</code></a> rules without
    considering whether those fonts are in fact used within a page are
    considered non-conformant. In cases where a font might be downloaded in
-   character fallback cases, user agents may download a font if it's listed
-   in a font list but is not actually used for a given text run.
+   character fallback cases, user agents may download a font if it's
+   contained within the computed value of <a href="#propdef-font-family"
+   title="font-family!!property">‘<code
+   class=property>font-family</code>’</a> for a given text run.
 
   <pre>
 @font-face {
@@ -5468,7 +5469,7 @@ <h3 id=feature-precedence><span class=secno>7.2 </span>Feature precedence</h3>
 
   <p>General and <a href="#font-specific"><em>font specific</em></a> font
    feature property settings are resolved in the order below, in ascending
-   precedence order. This ordering is used to construct a combined list of
+   order of precedence. This ordering is used to construct a combined list of
    font features that affect a given text run.
 
   <ol>
@@ -5492,14 +5493,15 @@ <h3 id=feature-precedence><span class=secno>7.2 </span>Feature precedence</h3>
     title="font-feature-settings!!property">‘<code
     class=property>font-feature-settings</code>’</a>. For example, setting
     a non-default value for the ‘<code
-    class=property>letter-spacing</code>’ property disables ligatures.
+    class=property>letter-spacing</code>’ property disables common
+    ligatures.
 
    <li>Font features implied by the value of the <a
     href="#propdef-font-variant" title="font-variant!!property">‘<code
     class=property>font-variant</code>’</a> property, the related <a
     href="#propdef-font-variant" title="font-variant!!property">‘<code
     class=property>font-variant</code>’</a> subproperties and any other CSS
-    property that may use OpenType features (e.g. the ‘<a
+    property that uses OpenType features (e.g. the ‘<a
     href="#propdef-font-kerning"><code
     class=property>font-kerning</code></a>’ property).
 
@@ -5524,7 +5526,7 @@ <h3 id=feature-precedence><span class=secno>7.2 </span>Feature precedence</h3>
    font lacks support for a given underlying font feature, text is simply
    rendered as if that font feature was not enabled; font fallback does not
    occur and no attempt is made to synthesize the feature except where
-   explicitly noted for specific properties.
+   explicitly defined for specific properties.
 
   <h3 id=feature-precedence-examples><span class=secno>7.3 </span>Feature
    precedence examples</h3>
@@ -5544,9 +5546,10 @@ <h3 id=feature-precedence-examples><span class=secno>7.3 </span>Feature
   </div>
 
   <div class=example>
-   <p>When the font-variant descriptor is used within an <a
-    href="#at-font-face-rule"><code>@font-face</code></a> rule, it only
-    applies to the font defined by that rule.</p>
+   <p>When the <a href="#descdef-font-variant"
+    title="font-variant!!descriptor">font-variant</a> descriptor is used
+    within an <a href="#at-font-face-rule"><code>@font-face</code></a> rule,
+    it only applies to the font defined by that rule.</p>
 
    <pre>@font-face {
   font-family: MainText;
@@ -5610,16 +5613,17 @@ <h3 id=feature-precedence-examples><span class=secno>7.3 </span>Feature
 span.special { font-variant-ligatures: no-discretionary-ligatures; }
 </pre>
 
-   <p>Adding an discretionary style rule with the <a
-    href="#at-font-face-rule"><code>@font-face</code></a> above:</p>
+   <p>Suppose one adds a rule using ‘<code
+    class=property>font-feature-settings</code>’ to enable discretionary
+    ligatures:</p>
 
    <pre>body         { font-family: main, Helvetica; }
 span         { font-feature-settings: "dlig"; }
 span.special { font-variant-ligatures: no-discretionary-ligatures; }
 </pre>
 
-   <p>Within spans of class "special", discretionary ligatures <em>will</em>
-    be rendered. This is because both the <a
+   <p>In this case, discretionary ligatures <em>will</em> be rendered within
+    spans of class "special". This is because both the <a
     href="#propdef-font-feature-settings"
     title="font-feature-settings!!property">‘<code
     class=property>font-feature-settings</code>’</a> and ‘<a