fix: typos across specs (w3c#5992)

Author: nschonni

biblio.ref

@@ -6440,7 +6440,7 @@
 %L WINDOWS-GLYPH-PROC
 %T Windows Glyph Processing
 %A John Hudson
-%I Microsoft Typogrraphy
+%I Microsoft Typography
 %U http://www.microsoft.com/typography/developers/opentype/default.htm
 
 %L WOFF

css-2015/Overview.bs

@@ -107,7 +107,7 @@ Background: The W3C Process and CSS</h3>
 
 		<dt>Recommendation (REC)
 		<dd>
-			This is the completed state of a W3C spec and represents a maintainance phase.
+			This is the completed state of a W3C spec and represents a maintenance phase.
 			At this point the WG only maintains an errata document
 			and occasionally publishes an updated edition that incorporates the errata back into the spec.
 	</dl>

css-2020/Overview.bs

@@ -318,7 +318,7 @@ Fairly Stable Modules with limited implementation experience</h3>
 		  [[!CSS-COLOR-4]]
 		<dd>
 			Extends and supersedes [[CSS-COLOR-3]],
-			further expanding the range of colors expressable in CSS.
+			further expanding the range of colors expressible in CSS.
 
 		<dt><a href="https://www.w3.org/TR/css-display-3/">CSS Display Module Level 3</a>
 		  [[CSS-DISPLAY-3]]

css-animations-2/Overview.bs

@@ -83,7 +83,7 @@ with the additions here into a complete level 2 specification.</p>
 
 Changes to any of the animation properties defined in this specification
 cause the corresponding {{CSSAnimation}} object and its associated objects
-to be updated according to the correspondance between these properties
+to be updated according to the correspondence between these properties
 and Web Animations concepts defined in [[#keyframes]].
 
 However, if the author modifies the animation
@@ -441,7 +441,7 @@ keyframe specifying each property.
 
 <div class='example'>
   For example, the following stylesheet defines two different animations
-  targetting the 'scale' property.
+  targeting the 'scale' property.
 
   <pre>
     @keyframes heartbeat {

css-backgrounds-3/box-shadow.src.html

@@ -55,7 +55,7 @@ <h2 class="no-num no-toc" id="abstract">Abstract</h2>
 
 <h2 class="no-num no-toc" id="status">Status of this document</h2>
 
-<p>This is a scrappy bit of an Editor'd Draft, is totally unstable,
+<p>This is a scrappy bit of an Editor's Draft, is totally unstable,
 and has no official status whatsoever. Treat it as you would a
 post-it note on the editors' desk.</p>
 <!--status-->

css-backgrounds-3/issues-lc-2010.html

@@ -123,7 +123,7 @@ <h1>CSS Backgrounds and Borders Level 3 Disposition of Comments</h1>
 </pre>
 <pre class="a" id="issue-12">
 Issue 12.
-Summary:  border-image shorthand inconcistent with CSS2.1 informative grammar
+Summary:  border-image shorthand inconsistent with CSS2.1 informative grammar
 From:     Yves
 Comment:  <a href="http://lists.w3.org/Archives/Public/www-style/2010Nov/0078.html">http://lists.w3.org/Archives/Public/www-style/2010Nov/0078.html</a>
 Response: <a href="http://lists.w3.org/Archives/Public/www-style/2010Nov/0405.html">http://lists.w3.org/Archives/Public/www-style/2010Nov/0405.html</a>

css-backgrounds-3/issues-lc-2010.txt

@@ -87,7 +87,7 @@ Closed:   Accepted
 Verified: http://lists.w3.org/Archives/Public/www-style/2010Dec/att-0356/css_response_from_pf.html
 ----
 Issue 12.
-Summary:  border-image shorthand inconcistent with CSS2.1 informative grammar
+Summary:  border-image shorthand inconsistent with CSS2.1 informative grammar
 From:     Yves
 Comment:  http://lists.w3.org/Archives/Public/www-style/2010Nov/0078.html
 Response: http://lists.w3.org/Archives/Public/www-style/2010Nov/0405.html

css-backgrounds-3/issues-lc-2012.txt

@@ -205,7 +205,7 @@ From:     Kang-Hao (Kenny) Lu
 Comment:  http://lists.w3.org/Archives/Public/www-style/2012Mar/0109.html
 Response: http://lists.w3.org/Archives/Public/www-style/2012Mar/0602.html
 Edit: 	  Added “otherwise the element's borders are
-	  invisble and the border image is drawn”.
+	  invisible and the border image is drawn”.
 Edit:	  Proposal for the rest has two options:
 	  (A) draw the table borders with invisible
 	  ink and then draw the image on top of it; or (B) an image border

css-backgrounds-3/transition-updated-cr-2017-09.md

@@ -8,7 +8,7 @@ CSS Backgrounds and Borders Module Level 3
 
 https://drafts.csswg.org/css-backgrounds-3/
 
-First Tuesday or Thursday after a sucessful transition decision.
+First Tuesday or Thursday after a successful transition decision.
 
 ## The document Abstract and Status sections
 

css-block-3/README

@@ -1,5 +1,5 @@
 This directory is just a placeholder for an eventual CSS Block Layout Level 3 module.
-In the rmeantime, please refer to CSS2 chapters 8, 9, 10.
+In the meantime, please refer to CSS2 chapters 8, 9, 10.
   https://www.w3.org/TR/CSS2/
 
 For anyone taking up this project, there existed a first draft by Bert Bos, see

css-box-3/block-layout.bs

@@ -1272,7 +1272,7 @@ depending on the percentages was undefined in CSS level 2.
 
 <div class=issue>
 <p>Some UAs implementing CSS level 2 try to solve the set of linear
-equations when <var>containing-block</var> is unkown:
+equations when <var>containing-block</var> is unknown:
 <blockquote>
 <p><var>margin</var> + <var>width</var> = <var>containing-block</var><br>
 <var>margin</var> = <var>percentage</var> &times; <var>containing-block</var>
@@ -1405,7 +1405,7 @@ area</em> or <em>border area</em> (depending on
   properties. See <a href="#Calculating">Calculating widths, heights
   and margins</a> below.
 
-  <dt>complex <dd>(Only on 'height'.) The same as ''heght/auto'', except
+  <dt>complex <dd>(Only on 'height'.) The same as ''height/auto'', except
   that elements with a <a>complex aspect ratio</a> (defined below) are
   considered to
   have an <a>intrinsic ratio</a>. More precisely: for the purposes
@@ -1977,7 +1977,7 @@ to be known in order to calculate the used height, or vice versa,
   <li>The tentative used width is calculated following the rules in
   the subsections below. If 'transform' is not ''none'', it is assumed
   to be 'rotate(0)' (i.e., the identity transform) for the purposes of
-  this calcutlation.
+  this calculation.
 
   <li>If the tentative used width is greater than 'max-width', the same
   rules are applied again, but this time using the computed value of
@@ -1994,7 +1994,7 @@ to be known in order to calculate the used height, or vice versa,
   <li>The tentative used height is calculated following the rules in
   the sections below. If 'transform' is not ''none'', it is assumed to
   be 'rotate(0)' (i.e., the identity transform) for the purposes of
-  this calcutlation.
+  this calculation.
 
   <li>If the tentative used height is greater than 'max-height', the
   same rules are applied again, but this time using the computed value
@@ -2095,7 +2095,7 @@ same rules apply, but with every occurrence of “left” replaced by
 “top,” “right” by “bottom,” “top” by “right,” “bottom” by “left”,
 “height” by “width” and “width” by “height.”
 
-<!-- '100vw' decided at ftf Sep 10, 2007. '100vh' is my sugggestion.
+<!-- '100vw' decided at ftf Sep 10, 2007. '100vh' is my suggestion.
 BB --> <p>For the purposes of evaluating percentages in the
 following subsections, if the width of the containing block is
 unknown, then assume the width is '100vw'. Likewise, if the height of

css-break-3/issues-cr-2016.bsi

@@ -61,7 +61,7 @@ Comment:  https://github.com/w3c/csswg-drafts/issues/1545
 Response: https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-414404715
 Changes:  https://github.com/w3c/csswg-drafts/commit/7f6b96445a4a5b60c80c816af4719e58cc2acb09#diff-83c5030d93d2408c7cf139946d26016e
 Closed:   Accepted / Retracted
-Veified:  https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-420639645
+Verified:  https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-420639645
 ----
 Issue 8.
 Summary:  Clarify aliasing mechanisms

css-break-3/issues-cr-2016.html

@@ -101,7 +101,7 @@ <h1>CSS Fragmentation Module Level 3 Disposition of Comments for 2016-01-14 CR</
 <span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-414404715'>https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-414404715</a></span>
 <span>Changes:  <a href='https://github.com/w3c/csswg-drafts/commit/7f6b96445a4a5b60c80c816af4719e58cc2acb09#diff-83c5030d93d2408c7cf139946d26016e'>https://github.com/w3c/csswg-drafts/commit/7f6b96445a4a5b60c80c816af4719e58cc2acb09#diff-83c5030d93d2408c7cf139946d26016e</a></span>
 <span class="a">Closed:   Accepted / Retracted</span>
-<span>Veified:  <a href='https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-420639645'>https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-420639645</a></span></pre>
+<span>Verified:  <a href='https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-420639645'>https://github.com/w3c/csswg-drafts/issues/1545#issuecomment-420639645</a></span></pre>
 <pre class=' a' id='issue-8'>
 <span>Issue 8. <a href='#issue-8'>#</a></span>
 <span>Summary:  Clarify aliasing mechanisms</span>

css-cascade-3/issues-cr-2016.bsi

@@ -8,7 +8,7 @@ From:     Sebastian Zartner
 Comment:  https://github.com/w3c/csswg-drafts/issues/142
 Changes:  https://github.com/w3c/csswg-drafts/commit/5919ac659a7bd197012feeb9e2fee24cefdaf880
 Closed:   Accepted
-Verified: Commenter submited patch
+Verified: Commenter submitted patch
 Resolved: Editorial
 ----
 Issue 2.

css-cascade-3/issues-cr-2016.html

@@ -48,7 +48,7 @@ <h1>CSS Cascading and Inheritance Module Level 3 Disposition of Comments for 201
 <span>Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/142'>https://github.com/w3c/csswg-drafts/issues/142</a></span>
 <span>Changes:  <a href='https://github.com/w3c/csswg-drafts/commit/5919ac659a7bd197012feeb9e2fee24cefdaf880'>https://github.com/w3c/csswg-drafts/commit/5919ac659a7bd197012feeb9e2fee24cefdaf880</a></span>
 <span class="a">Closed:   Accepted</span>
-<span class="a">Verified: Commenter submited patch</span>
+<span class="a">Verified: Commenter submitted patch</span>
 <span>Resolved: Editorial</span></pre>
 <pre class=' a' id='issue-2'>
 <span>Issue 2. <a href='#issue-2'>#</a></span>

css-cascade-4/Overview.bs

@@ -88,7 +88,7 @@ Module Interactions</h3>
 	For the purpose of this specification,
 	<a>text nodes</a> are treated as <a spec=css-display-3>element</a> children of their associated element,
 	and possess the full set of properties;
-	since they cannot be targetted by selectors
+	since they cannot be targeted by selectors
 	all of their computed values are assigned by <a href="#defaulting">defaulting</a>.
 
 <!--
@@ -1343,7 +1343,7 @@ Changes Since the 14 January 2016 Candidate Recommendation</h3>
 				<ins><p>For the purpose of this specification,
 				<a>text nodes</a> are treated as <a spec=css-display-3>element</a> children of their associated element,
 				and possess the full set of properties;
-				since they cannot be targetted by selectors
+				since they cannot be targeted by selectors
 				all of their computed values are assigned by <a href="#defaulting">defaulting</a>.</ins>
 			</blockquote>
 

css-cascade-5/Overview.bs

@@ -85,7 +85,7 @@ Module Interactions</h3>
 	For the purpose of this specification,
 	<a>text nodes</a> are treated as <a spec=css-display-3>element</a> children of their associated element,
 	and possess the full set of properties;
-	since they cannot be targetted by selectors
+	since they cannot be targeted by selectors
 	all of their computed values are assigned by <a href="#defaulting">defaulting</a>.
 
 <!--
@@ -1343,7 +1343,7 @@ Un-Named Layers</h5>
 			@layer url(base-headings.css);
 
 			/* bootstrap.css */
-			/* the intrnal names are hidden from access, subsumed in "base" */
+			/* the internal names are hidden from access, subsumed in "base" */
 			@layer base url(bootstrap-base.css);
 
 			/* author.css */

css-color-3/issues-lc-2008.html

@@ -557,7 +557,7 @@ <h3><a name="issue-26" id="issue-26">Issue 26</a></h3>
 <dt> <abbr title="Uniform Resource Locator">URL</abbr></dt>
 <dd><a href="http://www.w3.org/2009/11/03-CSS-minutes.html#item03" class="urlextern" title="http://www.w3.org/2009/11/03-CSS-minutes.html#item03"  rel="nofollow">minutes of F2F meeting, 2009-11-03</a> (have resolution)</dd>
 <dt> Resolution</dt>
-<dd>updated: do this in CSS4-color instead: “RESOLUTION: re-add a &#039;color-correction&#039; property with the two values &#039;default&#039; and &#039;srgb&#039;”, ”&#039;default&#039;: what UA would do if the property weren&#039;t specified at all. That can change over time. (E.g., at the moment we (Safari/Webkit) don&#039;t do color managament at all. But we may do so in the future.)”, ”&#039;srgb&#039;: All colors are presumed to be defined in the sRGB color space unless a more precise embedded profile is specified within content data. For images that do have a profile built into their data, that profile is used. For images that do not have a profile, the sRGB profile is used so that the colors in these images can be kept “in synch” with the colors specified in <abbr title="Cascading Style Sheets">CSS</abbr> and <abbr title="HyperText Markup Language">HTML</abbr>.”</dd>
+<dd>updated: do this in CSS4-color instead: “RESOLUTION: re-add a &#039;color-correction&#039; property with the two values &#039;default&#039; and &#039;srgb&#039;”, ”&#039;default&#039;: what UA would do if the property weren&#039;t specified at all. That can change over time. (E.g., at the moment we (Safari/Webkit) don&#039;t do color management at all. But we may do so in the future.)”, ”&#039;srgb&#039;: All colors are presumed to be defined in the sRGB color space unless a more precise embedded profile is specified within content data. For images that do have a profile built into their data, that profile is used. For images that do not have a profile, the sRGB profile is used so that the colors in these images can be kept “in synch” with the colors specified in <abbr title="Cascading Style Sheets">CSS</abbr> and <abbr title="HyperText Markup Language">HTML</abbr>.”</dd>
 
 <dt> Status</dt>
 <dd>no edit in CSS3-color.</dd>
@@ -635,7 +635,7 @@ <h3><a name="issue-30" id="issue-30">Issue 30</a></h3>
 </p>
 
 <p>
-IEC 61966-2-1: 1999: Multimedia systems and equipment — Colour measurement and management — Part 2-1: Colour management — Default RGB colour space — sRGB, International Electrotechnical Commission, 1999. ISBN 2-8318-4989-6 as ammended by Amendment A1:2003.
+IEC 61966-2-1: 1999: Multimedia systems and equipment — Colour measurement and management — Part 2-1: Colour management — Default RGB colour space — sRGB, International Electrotechnical Commission, 1999. ISBN 2-8318-4989-6 as amended by Amendment A1:2003.
 Available at <a href="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408" class="urlextern" title="http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408"  rel="nofollow">http://webstore.iec.ch/webstore/webstore.nsf/artnum/025408</a> and at <a href="http://www.colour.org/tc8-05/Docs/colorspace/61966-2-1.pdf" class="urlextern" title="http://www.colour.org/tc8-05/Docs/colorspace/61966-2-1.pdf"  rel="nofollow">http://www.colour.org/tc8-05/Docs/colorspace/61966-2-1.pdf</a> . 
 </p>
 

css-color-3/transition-cr-2017.md

@@ -8,7 +8,7 @@ CSS Color Module Level 3
 
 https://drafts.csswg.org/css-color-3/
 
-First Tuesday or Thursday after a sucessful transition decision.
+First Tuesday or Thursday after a successful transition decision.
 
 ## The document Abstract and Status sections
 
@@ -53,7 +53,7 @@ None
 
 [Test suite](https://test.csswg.org/harness/suite/css-color-3_dev/)
 
-The [implementatin report](https://test.csswg.org/harness/results/css-color-3_dev/grouped/) shows that
+The [implementation report](https://test.csswg.org/harness/results/css-color-3_dev/grouped/) shows that
 75 of 75 required tests meet CR exit criteria.
 
 More relevantly for this transition, there is [one test](https://test.csswg.org/harness/test/css-color-3_dev/single/t44-currentcolor-inherited-c/) for the substantive change, which is [passed by two implementations](https://test.csswg.org/harness/results/css-color-3_dev/grouped/t44-currentcolor-inherited-c/).