typo: Double words (#5951)

Co-authored-by: Rachel Andrew <rachel.andrew@edgeofmyseat.com>

css-2015/Overview.bs

@@ -556,7 +556,7 @@ Vendor-prefixing Unstable Features</h5>
 		This in turn allows UA vendors to retire
 		their prefixed syntax once the feature is stable,
 		with a lower risk of breaking existing content.
-		It also reduces the need occasionally felt by by some vendors
+		It also reduces the need occasionally felt by some vendors
 		to support a feature with the prefix of another vendor,
 		due to content depending on that syntax.
 	</details>

css-2017/Overview.bs

@@ -602,7 +602,7 @@ Vendor-prefixing Unstable Features</h5>
 		This in turn allows UA vendors to retire
 		their prefixed syntax once the feature is stable,
 		with a lower risk of breaking existing content.
-		It also reduces the need occasionally felt by by some vendors
+		It also reduces the need occasionally felt by some vendors
 		to support a feature with the prefix of another vendor,
 		due to content depending on that syntax.
 	</details>

css-2018/Overview.bs

@@ -622,7 +622,7 @@ Vendor-prefixing Unstable Features</h5>
 		This in turn allows UA vendors to retire
 		their prefixed syntax once the feature is stable,
 		with a lower risk of breaking existing content.
-		It also reduces the need occasionally felt by by some vendors
+		It also reduces the need occasionally felt by some vendors
 		to support a feature with the prefix of another vendor,
 		due to content depending on that syntax.
 	</details>

css-2020/Overview.bs

@@ -688,7 +688,7 @@ Vendor-prefixing Unstable Features</h5>
 		This in turn allows UA vendors to retire
 		their prefixed syntax once the feature is stable,
 		with a lower risk of breaking existing content.
-		It also reduces the need occasionally felt by by some vendors
+		It also reduces the need occasionally felt by some vendors
 		to support a feature with the prefix of another vendor,
 		due to content depending on that syntax.
 	</details>

css-align-3/Overview.bs

@@ -1715,7 +1715,7 @@ Effects on Sizing of Absolutely Positioned Boxes with Static-Position Insets</h3
 	the <a>available space</a> for calculating the <a>inline size</a>
 	is also affected by alignment.
 
-	Note: In [[CSS2]], the [=available space=] is keyed off of the the 'direction' property
+	Note: In [[CSS2]], the [=available space=] is keyed off of the 'direction' property
 	of the <a>static-position containing block</a>.
 	(See <a href="https://www.w3.org/TR/CSS2/visudet.html#abs-non-replaced-width">CSS2&sect;10.3.7</a>
 	and <a href="https://www.w3.org/TR/CSS2/visudet.html#abs-replaced-width">CSS2&sect;10.3.8</a>.)

css-backgrounds-3/Overview.bs

@@ -2377,7 +2377,7 @@ by default correspond to the border box, see 'border-image-outset'.
 
 <p>The four values of 'border-image-width' specify offsets that are used
 to divide the border image area into nine parts. They represent inward
-distances from the the top, right, bottom, and left sides of the
+distances from the top, right, bottom, and left sides of the
 area, respectively.
 
 <p>If there is only one component value,
@@ -2714,7 +2714,7 @@ has been moved to the <a href="https://www.w3.org/TR/css3-break/">CSS Fragmentat
     and appending blank shadows (''transparent 0 0 0 0'')
     with a corresponding ''box-shadow/inset'' keyword as needed
     to match the longer list
-    if the the shorter list is otherwise compatible with the longer one
+    if the shorter list is otherwise compatible with the longer one
 </table>
 
   <p>The 'box-shadow' property attaches one or more drop-shadows to the box.

css-box-3/block-layout.bs

@@ -2178,7 +2178,7 @@ set to the height of the largest rectangle that has a 2:1 ratio, has a
 height not greater than 150px, and has a width not greater than the
 device width.
 
-  <p class=issue>Theoretically, a device may be wider than than 300px
+  <p class=issue>Theoretically, a device may be wider than 300px
   but not tall enough for 150px. In that case the resulting replaced
   element will be too tall. But this is the formulation in CSS 2.1 and
   it seems not worth improving such an edge case.

css-cascade-4/Overview.bs

@@ -1376,7 +1376,7 @@ Additions Since Level 3</h3>
 	* Introduced ''supports()'' syntax for supports-conditional ''@import'' rules.
 	* Added [=encapsulation context=] to the [=cascade=] sort criteria
 		to accommodate Shadow DOM. [[DOM]]
-	* Defined the property two aliasing mechanisms CSS uses to support legacy syntaxes. See See [[#aliasing]].
+	* Defined the property two aliasing mechanisms CSS uses to support legacy syntaxes. See [[#aliasing]].
 <!--
 	* Added definition of how scoped styles would cascade
 		(deferred from Level 3)

css-cascade-5/Overview.bs

@@ -1529,7 +1529,7 @@ Additions Since Level 3</h3>
 	* Introduced ''supports()'' syntax for supports-conditional ''@import'' rules.
 	* Added [=encapsulation context=] to the [=cascade=] sort criteria
 		to accommodate Shadow DOM. [[DOM]]
-	* Defined the property two aliasing mechanisms CSS uses to support legacy syntaxes. See See [[#aliasing]].
+	* Defined the property two aliasing mechanisms CSS uses to support legacy syntaxes. See [[#aliasing]].
 <!--
 	* Added definition of how scoped styles would cascade
 		(deferred from Level 3)

css-color-4/Overview.bs

@@ -3148,7 +3148,7 @@ Profiled, Device-dependent Colors</h2>
 
 	An out of gamut color has component values
 	less than 0 or 0%, or greater than 1 or 100%.
-	These are are not invalid; instead, for display, they are
+	These are not invalid; instead, for display, they are
 	<a>gamut-mapped</a> using a relative colorimetric intent
 	which brings the values within the range 0/0% to 1/100%
 	at computed-value time.

css-color-4/math.js

@@ -12973,7 +12973,7 @@ return /******/ (function(modules) { // webpackBootstrap
 	   * `add`
 	   *
 	   * This function does not support collections (Array or Matrix), and does
-	   * not validate the number of of inputs.
+	   * not validate the number of inputs.
 	   *
 	   * @param  {number | BigNumber | Fraction | Complex | Unit} x   First value to add
 	   * @param  {number | BigNumber | Fraction | Complex} y          Second value to add
@@ -19115,7 +19115,7 @@ return /******/ (function(modules) { // webpackBootstrap
 	   * `multiply`
 	   *
 	   * This function does not support collections (Array or Matrix), and does
-	   * not validate the number of of inputs.
+	   * not validate the number of inputs.
 	   *
 	   * @param  {number | BigNumber | Fraction | Complex | Unit} x   First value to multiply
 	   * @param  {number | BigNumber | Fraction | Complex} y          Second value to multiply
@@ -19182,7 +19182,7 @@ return /******/ (function(modules) { // webpackBootstrap
 	   * `divide` and `inv`.
 	   *
 	   * This function does not support collections (Array or Matrix), and does
-	   * not validate the number of of inputs.
+	   * not validate the number of inputs.
 	   *
 	   * @param  {number | BigNumber | Fraction | Complex | Unit} x   Numerator
 	   * @param  {number | BigNumber | Fraction | Complex} y          Denominator

css-color-4/matrixmaker.html

@@ -5,7 +5,7 @@
 
 // Make matrices for converting to and from an arbitrary RGB colorspace,
 // given the x,y chromaticities of red, green, blue and white.
-// To use these matrices, the RGB components are assumed be be
+// To use these matrices, the RGB components are assumed be
 // linearized and in the range 0 to 1.
 // http://www.brucelindbloom.com/index.html?Eqn_RGB_XYZ_Matrix.html
 

css-device-adapt-1/Overview.bs

@@ -888,7 +888,7 @@ query affected by the viewport descriptors.
 
 It is recommended that authors do not write ''@viewport'' rules that
 rely on media queries whose evaluation is affected by viewport
-descriptors. Is is also recommended that the ''@viewport'' rule(s) is
+descriptors. It is also recommended that the ''@viewport'' rule(s) is
 placed as early in the document as possible to avoid unnecessary
 re-evaluation of media queries or reflows.
 

css-display-3/Overview.bs

@@ -1122,7 +1122,7 @@ Appendix A: Glossary</h2>
 			it essentially creates a new, independent layout environment:
 			except through the sizing of the box itself,
 			the layout of its descendants is (generally)
-			not affected by the the rules and contents of
+			not affected by the rules and contents of
 			the [=formatting context=] outside the box, and vice versa.
 
 			<p class="example">

css-exclusions-1/Exclusions.src.html

@@ -772,7 +772,7 @@ <h4 id="step-2-resolve-wrapping-contexts-layout-containing-blocks">Step 2: resol
 
         <p>In this step, starting from the 
             top of the <a href="https://www.w3.org/TR/CSS2/visuren.html#z-index">rendering tree</a> (see [[!CSS21]]), 
-            the the agent processes each containing block in two sub-steps.</p>
+            the agent processes each containing block in two sub-steps.</p>
 
         <h4 id="step-2-A-resolve-exclusions-position-and-size">Step 2-A: resolve the position and size of exclusion boxes</h4>
 
@@ -1217,7 +1217,7 @@ <h4 id="supported-basic-shapes">Supported Shapes</h4>
           <dd>
               <ul>
                   <li>
-                      The three values values represent 
+                      The three values represent 
                       <strong>cx</strong>, 
                       <strong>cy</strong>, 
                       and <strong>r</strong>. 

css-exclusions-1/Overview.bs

@@ -569,7 +569,7 @@ Step 1: resolve exclusion boxes belonging to each <a>wrapping context</a></h4>
 <h4 id="step-2">
 Step 2: resolve wrapping contexts and lay out containing blocks</h4>
 
-  In this step, starting from the top of the <a href="https://www.w3.org/TR/CSS2/visuren.html#z-index">rendering tree</a> (see [[!CSS21]]), the the agent processes each
+  In this step, starting from the top of the <a href="https://www.w3.org/TR/CSS2/visuren.html#z-index">rendering tree</a> (see [[!CSS21]]), the agent processes each
   containing block in two sub-steps.
 
 <h4 id="step-2-A">

css-fonts-4/Overview.bs

@@ -3232,7 +3232,7 @@ if all font style properties were set to their initial value.
 					3. If 'font-synthesis-style' has the value
 						'font-synthesis-style/auto',
 						then for variable fonts with a slnt axis
-						a match is is created by setting the slnt value
+						a match is created by setting the slnt value
 						with the specified oblique value;
 						otherwise,
 						a fallback match is produced
@@ -3262,7 +3262,7 @@ if all font style properties were set to their initial value.
 						in this stage.
 					3. If 'font-synthesis-style' has the value 'font-synthesis-style/auto',
 						then for variable fonts with a slnt axis
-						a match is is created by setting the slnt value
+						a match is created by setting the slnt value
 						with the specified oblique value;
 						otherwise,
 						a fallback match is produced
@@ -6578,7 +6578,7 @@ There is some risk that an attacker can spoof a native UI feature
 by determining the Operating System
 and using native-looking fonts appropriate to that Operating System.
 
-<h3 id="sp212">What temporary identifiers might this this specification create or expose to the web? </h3>
+<h3 id="sp212">What temporary identifiers might this specification create or expose to the web? </h3>
 
 None.
 
@@ -6682,7 +6682,7 @@ Changes
 	<li>Added a note about the generic emoji family and character support</li>
 	<li>Clarified that italic is not a fallback for oblique </li>
 	<li>Added warning on too large x-height</li>
-	<li>Added better example for for 'font-size-adjust'</li>
+	<li>Added better example for 'font-size-adjust'</li>
 	<li>Added example for ui-sans-serif </li>
 	<li>Miscellaneous editorial improvements, typo fixes, broken link fixes and markup improvements</li>
 </ul>

css-gcpm-3/2009-06-10.html

@@ -1336,20 +1336,20 @@ <h3 id=footnote-calls><span class=secno>6.3 </span>Footnote calls</h3>
 -->
    <!--
 <p class="issue">Should any white space characters between the
-note-call and and the preceding content be removed?
+note-call and the preceding content be removed?
 -->
    <!--
 <div class="example">
 The goal is to achieve this result:
 
 <pre>
-  ... some notion¹
+  ... some notion¹
 </pre>
 
 <p>rather than this:
 
 <pre>
-  ... some notion ¹
+  ... some notion ¹
 </pre>
 </div>
 -->
@@ -2795,7 +2795,7 @@ <h3>The &lsquo;<code class=css>pages</code>&rsquo; counter</h3>
 <div class=example>
 
 <p>This code has no effect on the &lsquo;<code class=css>pages</code>&rsquo; counter which cannot be
-changed by the style sheet. However, the the &lsquo;<code class=css>page</code>&rsquo; counter reset normally.
+changed by the style sheet. However, the &lsquo;<code class=css>page</code>&rsquo; counter reset normally.
 
 <pre>
 @page :right {

css-gcpm-3/2009-06-10.src.html

@@ -969,20 +969,20 @@ <h3>Footnote calls</h3>
 -->
 <!--
 <p class="issue">Should any white space characters between the
-note-call and and the preceding content be removed?
+note-call and the preceding content be removed?
 -->
 <!--
 <div class="example">
 The goal is to achieve this result:
 
 <pre>
-  ... some notion¹
+  ... some notion¹
 </pre>
 
 <p>rather than this:
 
 <pre>
-  ... some notion ¹
+  ... some notion ¹
 </pre>
 </div>
 -->
@@ -2058,7 +2058,7 @@ <h3>The ''pages'' counter</h3>
 <div class=example>
 
 <p>This code has no effect on the ''pages'' counter which cannot be
-changed by the style sheet. However, the the ''page'' counter reset normally.
+changed by the style sheet. However, the ''page'' counter reset normally.
 
 <pre>
 @page :right {

css-gcpm-3/Overview.bs

@@ -45,7 +45,7 @@ For readability they have not been repeated explicitly.
 <h2 id="running-headers-and-footers">
 	Running headers and footers
 </h2>
-[[CSS3PAGE]] describes the sixteen page margin boxes which can be used for running headers and footers, but does not describe a mechanism for inserting content in those boxes. This module provides two methods for for doing so. <dfn lt="named string">Named strings</dfn> copy text for reuse in margin boxes. <dfn id="running-elements0">Running elements</dfn> move elements (complete with style and structure) from the document to margin boxes.
+[[CSS3PAGE]] describes the sixteen page margin boxes which can be used for running headers and footers, but does not describe a mechanism for inserting content in those boxes. This module provides two methods for doing so. <dfn lt="named string">Named strings</dfn> copy text for reuse in margin boxes. <dfn id="running-elements0">Running elements</dfn> move elements (complete with style and structure) from the document to margin boxes.
 <h3 id="named-strings">
 	Named strings
 </h3>

css-grid-3/Overview.bs

@@ -118,7 +118,7 @@ Grid Item Placement</h3>
 <a>Grid items</a> are placed using these steps:
 <ol>
   <li>Place the items as if the [=masonry axis=] had ''grid-template-columns/none'' specified in that axis.
-  <li>For any items that were placed at the first (hypothetical) implicit line in the [=masonry axis=] in step 1, those items keep their placement in both axes as their final placement. They will be laid out first in each [=grid axis=] track and their [=grid axis=] placement is considered definite henceforth. All other items ignore their placement from step 1.  Any item with with a specified definite placement in the [=masonry axis=] that doesn't result in it being placed at the first implicit line in the [=masonry axis=] will be treated as having 'auto'-placement in that axis.
+  <li>For any items that were placed at the first (hypothetical) implicit line in the [=masonry axis=] in step 1, those items keep their placement in both axes as their final placement. They will be laid out first in each [=grid axis=] track and their [=grid axis=] placement is considered definite henceforth. All other items ignore their placement from step 1.  Any item with a specified definite placement in the [=masonry axis=] that doesn't result in it being placed at the first implicit line in the [=masonry axis=] will be treated as having 'auto'-placement in that axis.
   <li>Place items using the <a href="#masonry-layout-algorithm">Masonry layout algorithm</a> below.
 </ol>
 

css-highlight-api-1/Overview.bs

@@ -162,7 +162,7 @@ Creating Custom Highlights</h3>
 
 	The <dfn for="custom highlight">name</dfn> of a [=custom highlight=]
 	is represented by its {{Highlight/name}} attribute,
-	which must must be a valid <<ident-token>>.
+	which must be a valid <<ident-token>>.
 
 	<xmp class="idl">
 	[Exposed=Window]

css-images-3/Overview.bs

@@ -112,11 +112,11 @@ Image Values: the <<image>> type {#image-values}
 	However, <a>invalid images</a> can trigger error-handling clauses
 	in some contexts.
 	For example, an <a>invalid image</a> in 'list-style-image'
-	is treated as ''list-style-type/none'',
+	it is treated as ''list-style-type/none'',
 	allowing the 'list-style-type' to render in its place. [[CSS2]]
 
 	While an image is loading,
-	is is a <dfn export>loading image</dfn>.
+	is a <dfn export>loading image</dfn>.
 	[=Loading images=] are <em>not</em> [=invalid images=],
 	but have similar behavior:
 	they are rendered as a solid-color ''transparent'' image with no [=natural dimensions=],
@@ -669,7 +669,7 @@ Radial Gradients: the ''radial-gradient()'' notation {#radial-gradients}
 	if the center is on a <a>gradient box</a> edge and ''closest-side'' or ''closest-corner'' is specified
 	or if the size and shape are given explicitly and either of the radiuses is zero.
 	In these degenerate cases,
-	the gradient must be be rendered as follows:
+	the gradient must be rendered as follows:
 
 	: If the <a>ending shape</a> is a circle with zero radius:
 	:: Render as if the <a>ending shape</a> was

css-images-4/Overview.bs

@@ -85,11 +85,11 @@ Value Definitions {#values}
 	However, <a>invalid images</a> can trigger error-handling clauses
 	in some contexts.
 	For example, an <a>invalid image</a> in 'list-style-image'
-	is treated as ''list-style-type/none'',
+	it is treated as ''list-style-type/none'',
 	allowing the 'list-style-type' to render in its place. [[CSS2]]
 
 	While an image is loading,
-	is is a <dfn export>loading image</dfn>.
+	is a <dfn export>loading image</dfn>.
 	[=Loading images=] are <em>not</em> [=invalid images=],
 	but have similar behavior:
 	they are rendered as a solid-color ''transparent'' image with no [=natural dimensions=],

css-inline-3/Overview.bs

@@ -1404,7 +1404,7 @@ Inline Box Heights: the 'inline-sizing' property</h3>
 			is sized and positioned to fit (possibly hypothetical) text
 			from its [=first available font=].
 			This specification does not specify how.
-			A UA may, e.g., use the the maximum ascender and descender of the font.
+			A UA may, e.g., use the maximum ascender and descender of the font.
 			(This would ensure that glyphs with parts above or below the em-box
 			still fall within the content area,
 			but leads to differently sized boxes for different fonts.)

css-lists-3/Overview.bs

@@ -1035,7 +1035,7 @@ Inheriting Counters</h4>
 			[=map/For each=] |source counter| of |value source|,
 			if |element counters| [=set/contains=] a [=counter=]
 			with the same [=name=] and [=creator=],
-			then set the the [=value=] of that counter
+			then set the [=value=] of that counter
 			to |source counter|'s [=value=].
 	</div>