minor corrections/edits

Author: John Daggett

css3-fonts/Overview.html

@@ -1960,7 +1960,7 @@ <h3 id=font-face-rule><span class=secno>4.1 </span>The @font-face rule</h3>
   <p>Downloaded fonts are only available to documents that reference them,
    the process of activating these fonts should not make them available to
    other applications or to documents that don't directly link to the same
-   font. User agent implementors might consider it convenient to use
+   font. User agent implementers might consider it convenient to use
    downloaded fonts when rendering characters in other documents for which no
    other available font exists as part of the system font fallback procedure.
    This would cause a security leak since the contents of one page would be
@@ -2127,7 +2127,7 @@ <h3 id=src-desc><span class=secno>4.3 </span>Font reference: the <a
    format hints "truetype" and "opentype" must be considered as synonymous; a
    format hint of "opentype" does not imply that the font contains Postscript
    CFF style glyph data or that it contains OpenType layout information (see
-   Appendix A for more background on this).
+   Appendix B for more background on this).
 
   <p>When authors would prefer to use a locally available copy of a given
    font and download it if it's not, local() can be used. The locally
@@ -3676,6 +3676,18 @@ <h3 id=font-variant-alternates-prop><span class=secno>6.8 </span>Alternates
    in addition to the default glyph for that character. This property
    provides control over the selection of these alternate glyphs.
 
+  <p>In cases where multiple alternates are possible, authors define a <a
+   href="#ltfeature-value-namegt"><code>&lt;feature-value-name&gt;</code></a>
+   using the <code>@font-feature-values</code> rule described below to
+   indicate the specific alternate to be used. The nature of these alternates
+   is font specific, so the rule defines values for a specific font family or
+   set of families. When a particular value has not been defined for a given
+   family, the named value is treated as if the feature had omitted from the
+   style rule. If a given value is outside the range supported by a given
+   font, the value is ignored. These values never apply to generic font
+   families, nor to families selected as part of system font fallback. Values
+   that behave this way are marked as <em>font specific</em>.
+
   <p>Individual values have the following meanings:
 
   <dl>
@@ -3782,18 +3794,6 @@ <h3 id=font-variant-alternates-prop><span class=secno>6.8 </span>Alternates
     font scaling.
   </dl>
 
-  <p>In cases where multiple alternates are possible, authors define a <a
-   href="#ltfeature-value-namegt"><code>&lt;feature-value-name&gt;</code></a>
-   using the <code>@font-feature-values</code> rule described below to
-   indicate the specific alternate to be used. The nature of these alternates
-   is font specific, so the rule is defined per font family. When a
-   particular value has not been defined for a given family, the named value
-   is treated as if the feature had omitted from the style rule. If a given
-   value is outside the range supported by a given font, the value is
-   ignored. These values never apply to generic font families, nor to
-   families selected as part of system font fallback. Values that behave this
-   way are marked as <em>font specific</em>.
-
   <div class=example>
    <p>The example below uses stylistic sets and swashes for section titles
     but not for the main title.</p>
@@ -4606,7 +4606,7 @@ <h2 class=no-num id=same-origin-restriction>Appendix A: Same-origin
    explicitly allow cross-site downloading of font data using the
    <code>Access-Control-Allow-Origin</code> HTTP header.
 
-  <p class=issue>Some implementors feel a same-origin restriction should be
+  <p class=issue>Some implementers feel a same-origin restriction should be
    the default for all new resource types while others feel strongly that an
    opt-in strategy usuable for all resource types would be a better mechanism
    and that the default should always be to allow cross-origin linking for
@@ -4625,7 +4625,7 @@ <h2 class=no-num id=platform-props-to-css>Appendix B: Mapping platform font
    font formats used; they can be used to specify bitmap fonts, Type1 fonts,
    SVG fonts in addition to the common TrueType and OpenType fonts. But there
    are facets of the TrueType and OpenType formats that often cause confusion
-   for authors and present challenges to implementors on different platforms.
+   for authors and present challenges to implementers on different platforms.
 
 
   <p>Originally developed at Apple, TrueType was designed as an outline font
@@ -4685,6 +4685,9 @@ <h2 class=no-num id=platform-props-to-css>Appendix B: Mapping platform font
    Mac OS X. Apple has indicated it intends to support complex script
    rendering using OpenType font features in the future.
 
+  <p class=issue>Need to define normatively how WWS names are handled across
+   platforms.
+
   <h2 class=no-num id=font-licensing>Appendix C: Font licensing issues</h2>
 
   <p><em>This appendix is informative only.</em>