Fix mistakes (w3c#7729)

Author: Ivan Panchenko

css-fonts-4/Overview.bs

@@ -2804,7 +2804,7 @@ Each <<urange>> value is a
 <a href="https://www.w3.org/TR/CSS21/syndata.html#tokenization"><code title="UNICODE-RANGE token">UNICODE-RANGE</code></a>
 token made up of a "U+" or "u+" prefix
 followed by a codepoint range in one of the three forms listed below.
-Ranges that do not fit one of the these forms are invalid
+Ranges that do not fit one of these forms are invalid
 and cause the declaration to be ignored.
 
 <dl>
@@ -3184,7 +3184,7 @@ Font fetching requirements</h4>
 
 Note: The implications of this for authors are that fonts
 will typically not be loaded cross-origin unless authors specifically
-takes steps to permit cross-origin loads. Sites can explicitly allow
+take steps to permit cross-origin loads. Sites can explicitly allow
 cross-site loading of font data using the <code>Access-Control-Allow-Origin</code>
 HTTP header.  For other schemes, no explicit mechanism to allow
 cross-origin loading, beyond what is permitted by the
@@ -3197,15 +3197,15 @@ algorithm, is defined or required.
 
 <div class="example" id="ex-cross-origin">
 	For the examples given below, assume that a document is located at
-	<code>https://example.com/page.html</code> and all URL's link to valid
+	<code>https://example.com/page.html</code> and all URLs link to valid
 	font resources supported by the user agent.
 
 	Fonts defined with the 'src!!descriptor' descriptor values below will be loaded:
 
 <pre>/* same origin (i.e. domain, scheme, port match document) */
 src: url(fonts/simple.woff);
 
-/* data url's with no redirects are treated as same origin */
+/* data urls with no redirects are treated as same origin */
 src: url("data:application/font-woff;base64,...");
 
 /* cross origin, different domain */
@@ -3728,7 +3728,7 @@ if all font style properties were set to their initial value.
 		present in this group which can support a range of
 		'font-stretch!!property', 'font-style!!property', or 'font-weight!!property' properties. In
 		this case, the algorithm proceeds as if each supported combination of
-		values are a unique font in the set. If such a font is ultimately
+		values is a unique font in the set. If such a font is ultimately
 		selected by this algorithm, particular values for
 		'font-stretch!!property', 'font-style!!property', and 'font-weight!!property' must be applied
 		before any layout or rendering occurs. The application of these values
@@ -4006,7 +4006,7 @@ if all font style properties were set to their initial value.
 		<!-- resolution on the above: http://lists.w3.org/Archives/Public/www-style/2012Nov/0292.html -->
 
 	7. If there are no more font families to be evaluated and no matching
-		face has been found, then the user agent performs a <dfn>installed font
+		face has been found, then the user agent performs an <dfn>installed font
 		fallback</dfn> procedure to find the best match for the character to be
 		rendered.  The result of this procedure can vary across user agents.
 
@@ -5440,7 +5440,7 @@ the <dfn lt="font feature value declaration">font feature value declarations</df
 where the declaration's name can be any [=identifier=],
 and the value must be a list of one or more non-negative <<integer>>s.
 
-The <<feature-value-block>>s accepts any declaration name;
+The <<feature-value-block>>s accept any declaration name;
 these names must be identifiers,
 per standard CSS syntax rules,
 and are [=case-sensitive=]
@@ -6277,7 +6277,7 @@ text run.
 3. The language specified by the inherited value of lang/xml:lang is applied.
 
 4. If the font is defined via an ''@font-face'' rule, the font language override
-	implied by the 'font-language-override!!descriptor' descriptor in the ''@font-face'' rule are applied.
+	implied by the 'font-language-override!!descriptor' descriptor in the ''@font-face'' rule is applied.
 
 5. If the font is defined via an ''@font-face'' rule, that ''@font-face'' rule includes
     at least one valid 'font-named-instance' descriptor
@@ -7154,7 +7154,7 @@ Overriding a colors from a palette: The 'override-colors!!descriptor' descriptor
     The '@font-palette-values/override-colors' descriptor takes
     a comma-separated list of palette index entries and colors.
     Each item in the comma-separated list represents a tuple of
-    an entry into the palette an a color to replace it with.
+    an entry into the palette and a color to replace it with.
 
     For each key/value pair in the value of this descriptor,
     the color with that key in the initial palette (i.e. by using the 'base-palette' descriptor)
@@ -7248,7 +7248,7 @@ A different UA might wish instead to use the same mechanical cluster fallback al
 that it would use for any arbitrary cluster.
 
 Variation selectors other than FE0E VARIATION SELECTOR-15 and U+FE0F VARIATION SELECTOR-16
-must not have any affect on font selection.
+must not have any effect on font selection.
 If one of these variation selectors is present,
 but unsupported by the font previously selected,
 the variation selector is ignored.
@@ -7921,13 +7921,13 @@ None.
 
 <a href="#font-fetching-requirements">For font loads</a>, user agents must use the
 potentially CORS-enabled fetch method defined by the [[!HTML]] specification
-for URL’s defined within @font-face rules.
+for URLs defined within @font-face rules.
 When fetching, user agents must use "Anonymous" mode,
 set the referrer source to the stylesheet’s URL
 and set the origin to the URL of the containing document.
 
 Thus, fonts will typically not be loaded cross-origin
-unless authors specifically takes steps to permit cross-origin loads.
+unless authors specifically take steps to permit cross-origin loads.
 
 <h3 id="sp214">How does this specification work in the context of a user agent’s Private Browsing or "incognito" mode? </h3>
 
@@ -8125,7 +8125,7 @@ Changes
 	<li>Avoiding cross-site font leakage amde RFC-2119 MUST</li>
 	<li>Clarified monochromatic fallback on color fonts</li>
 	<li>Removed remaining references to min-font-size, max-font-size</li>
-	<li>Clarified that color names are ACII case insensitive</li>
+	<li>Clarified that color names are ASCII case insensitive</li>
 	<li>Added the value none to font-palette</li>
 	<li>Marked font-palette and @font-palette-values as at-risk</li>
 	<li>Aligned value definition reference across all specs.</li>
@@ -8279,4 +8279,4 @@ This summarizes the changes in CSS Fonts 4, compared to CSS Fonts 3.
  -->
 	<wpt hidden>
 
-</wpt>
+</wpt>

css-writing-modes-3/Overview.bs

@@ -953,7 +953,7 @@ Supporting SVG1.1 'writing-mode' values in CSS syntax</h5>
   </table>
 
   <p class="note">The SVG1.1 values were also present
-    in an older of the CSS 'writing-mode' specification,
+    in an older version of the CSS 'writing-mode' specification,
     which is obsoleted by this specification.
     The additional ''tb-lr'' value of that revision
     is replaced by ''vertical-lr''.
@@ -1381,7 +1381,7 @@ Mixed Vertical Orientations</h4>
     When 'text-orientation' is ''mixed'',
     the UA must determine the orientation of each <a>typographic character unit</a>
     by its <code>Vertical_Orientation</code> property:
-    <a href="#typeset-upright">typeseting it upright</a>
+    <a href="#typeset-upright">typesetting it upright</a>
     if its orientation property is <code>U</code>, <code>Tu</code>, or <code>Tr</code>;
     or <a href="#typeset-sideways">typesetting it sideways</a> (90&deg; clockwise from horizontal)
     if its orientation property is <code>R</code>.