[css-fonts] fixes based on comments

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-24-may-2013>Editor's Draft 24
+   <h2 class="no-num no-toc" id=editors-draft-29-may-2013>Editor's Draft 29
     May 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-20130524/">http://www.w3.org/TR/2013/ED-css3-fonts-20130524/</a> -->
+     <!-- <dd><a href="http://www.w3.org/TR/2013/ED-css3-fonts-20130529/">http://www.w3.org/TR/2013/ED-css3-fonts-20130529/</a> -->
 
 
     <dt>Latest version:
@@ -713,7 +713,8 @@ <h3 id=font-family-prop><span class=secno>3.1 </span>Font family: the <a
     alternative for improved robustness.
   </dl>
 
-  <p>Font family names must either be given quoted as <a
+  <p>Font family names other than generic families must either be given
+   quoted as <a
    href="//www.w3.org/TR/CSS21/syndata.html#strings">strings,</a> or unquoted
    as a sequence of one or more <a
    href="//www.w3.org/TR/CSS21/syndata.html#value-def-identifier">identifiers.</a>
@@ -1488,8 +1489,8 @@ <h3 id=font-size-prop><span class=secno>3.5 </span>Font size: the <a
 
   <p class=note><em><strong>Note 1.</strong> To preserve readability, an UA
    applying these guidelines should nevertheless avoid creating font-size
-   resulting in less than 9 device pixels per EM unit on a computer display
-   .</em>
+   resulting in less than 9 device pixels per EM unit on a computer
+   display.</em>
 
   <p class=note><em><strong>Note 2.</strong> In CSS1, the suggested scaling
    factor between adjacent indexes was 1.5 which user experience proved to be
@@ -2218,13 +2219,14 @@ <h3 id=src-desc><span class=secno>4.3 </span>Font reference: the <a
 
   <p>This descriptor specifies the resource containing font data. It is
    required for the <code>@font-face</code> rule to be valid. Its value is a
-   prioritized, comma-separated list of external references or locally
-   installed font face names. When a font is needed the user agent iterates
-   over the set of references listed, using the first one it can successfully
-   activate. Fonts containing invalid data or local font faces that are not
-   found are ignored and the user agent loads the next font in the list.
-
-  <p>As with other URLs in CSS, the URL may be partial, in which case it is
+   prioritized, comma-separated list of external references or
+   locally-installed font face names. When a font is needed the user agent
+   iterates over the set of references listed, using the first one it can
+   successfully activate. Fonts containing invalid data or local font faces
+   that are not found are ignored and the user agent loads the next font in
+   the list.
+
+  <p>As with other URLs in CSS, the URL may be relative, in which case it is
    resolved relative to the location of the style sheet containing the <span
    class=index-inst id=font-face0
    title="@font-face"><code>@font-face</code></span> rule. In the case of SVG
@@ -2324,8 +2326,8 @@ <h3 id=src-desc><span class=secno>4.3 </span>Font reference: the <a
    font and download it if it's not, <code>local()</code> can be used. The
    locally-installed <dfn
    id=font-face-name-value><var>&lt;font-face-name&gt;</var></dfn> argument
-   is a format-specific string that uniquely identifies a single font face
-   within a larger family. The syntax for a <a
+   to <code>local()</code> is a format-specific string that uniquely
+   identifies a single font face within a larger family. The syntax for a <a
    href="#font-face-name-value"><var>&lt;font-face-name&gt;</var></a> is a
    unique font face name enclosed by "local(" and ")". The name can
    optionally be enclosed in quotes. If unquoted, the unquoted font family
@@ -2528,8 +2530,8 @@ <h3 id=font-prop-desc><span class=secno>4.4 </span>Font property
    style implied by the underlying font data. This allows authors to combine
    faces in flexible combinations, even in situations where the original font
    data was arranged differently. User agents that implement synthetic
-   bolding and obliqueing must only apply synthetic styling in cases where
-   the font descriptors imply this is needed, rather than based on the style
+   bolding and obliquing must only apply synthetic styling in cases where the
+   font descriptors imply this is needed, rather than based on the style
    attributes implied by the font data.
 
   <h3 id=unicode-range-desc><span class=secno>4.5 </span>Character range: the
@@ -2598,7 +2600,7 @@ <h3 id=unicode-range-desc><span class=secno>4.5 </span>Character range: the
    digit (e.g. "U+0???" = "U+0000-0FFF"). Wildcard ranges that extend beyond
    the range of valid Unicode codepoints are invalid. Because of this, the
    maximum number of trailing ‘<code class=css>?</code>’ wildcard
-   characters is four, even though the <a
+   characters is five, even though the <a
    href="http://www.w3.org/TR/CSS21/syndata.html#tokenization"><code
    title="UNICODE-RANGE token">UNICODE-RANGE</code></a> token accepts six.
 
@@ -2611,7 +2613,7 @@ <h3 id=unicode-range-desc><span class=secno>4.5 </span>Character range: the
    the list of ranges into a list that is different but represents the same
    set of codepoints.
 
-  <p>The associated font may not contain glyphs for the entire set of
+  <p>The associated font might not contain glyphs for the entire set of
    codepoints defined by the ‘<a href="#descdef-unicode-range"><code
    class=property>unicode-range</code></a>’ descriptor. When the font is
    used the effective <a href="#character-map"><em>character map</em></a> is
@@ -2878,7 +2880,7 @@ <h3 id=font-face-loading><span class=secno>4.8 </span>Font loading
    guidelines</h3>
 
   <p>The <code>@font-face</code> rule is designed to allow lazy loading of
-   fonts, fonts are only downloaded when needed for use within a document. A
+   font resources that are only downloaded when used within a document. A
    stylesheet can include <code>@font-face</code> rules for a library of
    fonts of which only a select set are used; user agents must only download
    those fonts that are referred to within the style rules applicable to a
@@ -3021,15 +3023,15 @@ <h3 id=font-family-casing><span class=secno>5.1 </span>Case sensitivity of
    normalization.
 
   <p class=note> For authors this means that font family names are matched
-   case insensitively, whether or not those names exist in a platform font or
-   in the <code>@font-face</code> rules contained in a stylesheet. Authors
-   should take care to ensure that names use a character sequence consistent
-   with the actual font family name, particularly when using combining
-   characters such as diacritical marks. For example, a family name that
-   contains an uppercase A (U+0041) followed by a combining ring (U+030A)
-   will <strong>not</strong> match a name that looks identical but which uses
-   the precomposed lowercase a-ring character (U+00E5) instead of the
-   combining sequence.
+   case insensitively, whether those names exist in a platform font or in the
+   <code>@font-face</code> rules contained in a stylesheet. Authors should
+   take care to ensure that names use a character sequence consistent with
+   the actual font family name, particularly when using combining characters
+   such as diacritical marks. For example, a family name that contains an
+   uppercase A (U+0041) followed by a combining ring (U+030A) will
+   <strong>not</strong> match a name that looks identical but which uses the
+   precomposed lowercase a-ring character (U+00E5) instead of the combining
+   sequence.
 
   <h3 id=font-style-matching><span class=secno>5.2 </span>Matching font
    styles</h3>
@@ -3489,7 +3491,7 @@ <h3 id=font-kerning-prop><span class=secno>6.3 </span>Kerning: the <a
    User agents must also support fonts that only support kerning via data
    contained in a ‘<code class=property>kern</code>’ font table, as
    detailed in the OpenType specification. Authors may prefer to disable
-   kerning in situations where performance is more important that precise
+   kerning in situations where performance is more important than precise
    appearance. If the ‘<code class=property>letter-spacing</code>’
    property is defined, kerning adjustments are considered part of the
    default spacing, letter spacing adjustments are made after kerning has
@@ -5049,6 +5051,13 @@ <h3 id=font-feature-settings-prop><span class=secno>6.12 </span>Low-level
 font-feature-settings: dlig;           /* invalid, tag must be a string */
 </pre>
 
+  <p>When values greater than the range supported by the font are specified,
+   the behavior is explicitly undefined. For boolean features, in general
+   these will enable the feature. For non-boolean features, out of range
+   values will in general be equivalent to a 0 value. However, in both cases
+   the exact behavior will depend upon the way the font is designed
+   (specifically, which type of lookup is used to define the feature).
+
   <p>Authors should generally use ‘<a href="#propdef-font-variant"><code
    class=property>font-variant</code></a>’ and its related subproperties
    whenever possible and only use this property for special cases where its