fix: typos across specs (#9164)

Author: nschonni

bin/issuegen.pl

@@ -51,7 +51,7 @@
 This is a script that converts a plaintext (.txt or .bsi) issues list
 into a color-coded HTML file of the same name (but .html file extension).
 The input is itself a presentable, easily-editable file designed
-mostly for the editor’s convenenience.
+mostly for the editor’s convenience.
 
 The original purpose of this format is to create a Disposition of
 Comments for the W3C's LCWD->CR transition process. However, it is
@@ -230,7 +230,7 @@ sub header {
   }
   die "Error: missing document URL or title.\n" unless ($url && $title);
 
-  # Process URL to get status, date, shorname
+  # Process URL to get status, date, shortname
   my $status = 'Draft';
   my $date = $1 if ($inFile =~ /([\d-]+)/);
   if ($url =~ /([A-Z]{2})-([a-z0-9-]+)-(\d{8})/) {

css-anchor-position-1/Overview.bs

@@ -1249,7 +1249,7 @@ this will <em>usually</em> mean you wouldn't see a "base" ''anchor(auto)''
 show up in the final styles at all,
 but if that does happen
 (it's specified in a property
-that isn't overriden by anything in the [=position fallback list=]),
+that isn't overridden by anything in the [=position fallback list=]),
 the only effect of the ''anchor()/auto''/''auto-same''
 is to resolve to the appropriate side keyword.
 

css-animations-2/Overview.bs

@@ -927,7 +927,7 @@ console.log(anim.playState); // Should be 'running'.
       to re-use the [=cascade=],
       to handle non-percentage keyframe offsets,
       to handle keyframes with offsets outside the [0,1] range,
-      and to use the value of 'animation-composition' as the default composit.
+      and to use the value of 'animation-composition' as the default composite.
     <li>Reduced the cases where ''display: none'' cancel an animation.
       (<a href="https://github.com/w3c/csswg-drafts/issues/6429">Issue 6429</a>)
     <li>Cross-linked to [[css-values-4#linked-properties]] to define how the various 'animation-*' properties interact.

css-cascade-6/Overview.bs

@@ -156,7 +156,7 @@ Cascade Sorting Order</h3>
 			[=scoped style rule=] [=subject=] wins.
 			For this purpose,
 			style rules without a [=scoping root=]
-			are considered to have inifinite proximity hops.
+			are considered to have infinite proximity hops.
 
 		<dt id='cascade-order'>Order of Appearance
 		<dd>

css-color-4/Overview.bs

@@ -818,7 +818,7 @@ Representing Colors: the <<color>> type</h2>
 	The [=color functions=] available in Level 4 are
 	* ''rgb()'' and its ''rgba()'' alias,
 		which (like the [=hex color notation=]) specify sRGB colors directly
-		by their red/green/blue/alpha chanels.
+		by their red/green/blue/alpha channels.
 	* ''hsl()'' and its ''hsla()'' alias,
 		which specify sRGB colors
 		by hue, saturation, and lightness
@@ -1819,7 +1819,7 @@ System Colors</h3>
 	<wpt>
 		parsing/color-valid.html
 		system-color-compute.html
-		system-color-hightlights-vs-getSelection-001.html
+		system-color-highlights-vs-getSelection-001.html
 	</wpt>
 
 	Note: As with all other [=CSS/keywords=],
@@ -3019,7 +3019,7 @@ Device-independent Colors: CIE Lab and LCH, Oklab and Oklch</h2>
 	and computation of the visual difference between two colors.
 
 	To compensate for this,
-	formulae to predict the visual difference betwen two colors
+	formulae to predict the visual difference between two colors
 	(delta E)
 	have been made more accurate over time
 	(but also, much more complex to compute).
@@ -3038,7 +3038,7 @@ Device-independent Colors: CIE Lab and LCH, Oklab and Oklch</h2>
 	Recently, Oklab,
 	an improved Lab-like space has been developed [[!Oklab]].
 	The corresponding polar form is called Oklch.
-	It was produced by numerical optimisation
+	It was produced by numerical optimization
 	of a large dataset of visually similar colors,
 	and has improved hue linearity,
 	hue uniformity,
@@ -4329,7 +4329,7 @@ with white point |dest-white|:
 	Otherwise, let |dest-rect| be |dest|.
 
 	<li id="convert-fromXYZ">Convert |xyz| to |dest|,
-	followed by appying any transfer function (gamma encoding),
+	followed by applying any transfer function (gamma encoding),
 	producing |col2|.
 
 	<li id="convert-display">If |dest| is a physical output color space, such as a display,
@@ -4390,7 +4390,7 @@ Color Interpolation</h2>
 	  (which has a colorimetric interpretation, which is all of them except for device-cmyk and even then, only in corner cases)
 	- allowing individual specifications to override this
 	  (for example compositing should be in linear-light XYZ)
-	  (for example, clor-mix defaults to LCH but allows other spaced to be explicitly specified)
+	  (for example, color-mix defaults to LCH but allows other spaced to be explicitly specified)
 	- maintaining Web compat with special-case where all the colors to be interpolated use legacy sRGB
 	- providing an opt-in for sRGB colors
 
@@ -4947,7 +4947,7 @@ Note: This section provides important context for the specific requirements desc
 	an in-gamut color.
 
 	Gamut mapping is the process of finding an in-gamut color
-	with the least objectionable change in visual apprearance.
+	with the least objectionable change in visual appearance.
 
 <h4 id="GM-clip">
 Clipping</h4>
@@ -4985,7 +4985,7 @@ Closest Color (MINDE)</h4>
 	in a perceptually uniform color space,
 	by finding the closest in-gamut color
 	(so-called minimum ΔE or <dfn export>MINDE</dfn>).
-	Clearly, the sucess of this technique
+	Clearly, the success of this technique
 	depends on
 	the degree of uniformity of the gamut mapping color space
 	and the predictive accuracy of the deltaE function used.
@@ -6610,7 +6610,7 @@ Changes</h2>
 	<!-- to 10 May 2023 -->
 	<li>Clarified for legacy syntax that color components must be all-percentage or all-number</li>
 	<li>Added examples of specified out of range alpha, with and without calc()</li>
-	<li>Placed examples of serializing with trimmed trailing zeroes clorer to the relevant text</li>
+	<li>Placed examples of serializing with trimmed trailing zeroes colorer to the relevant text</li>
 	<li>clarified example, used value of text-shadow</li>
 	<li>Clarified resolving currentColor</li>
 	<li>Updated acknowledgments</li>
@@ -6653,7 +6653,7 @@ Changes</h2>
 	<li>Moved definitions of valid color, invalid color, out of gamut and in gamut to terminology section</li>
 	<li>Fixed definition of "longer" hue interpolation</li>
 	<li>Further clarified the concept of a host syntax</li>
-	<li>Acessibility improvements for color swatches</li>
+	<li>Accessibility improvements for color swatches</li>
 	<li>Made explicit that legacy forms do not support "none"</li>
 	<li>Remove "none" from the hue production, as it is not allowed in legacy syntax</li>
 	<li>Removed some dangling references to CMYK and CMYKOGV, moved to CSS Color5</li>
@@ -6790,7 +6790,7 @@ Changes</h2>
 	<li>Simplified ''color()'' syntax by removing the fallback options</li>
 	<li>Clarified the types of ICC profile that may be linked from @color-profile</li>
 	<li>Support for the rare ICC Named Colors was removed</li>
-	<li>Improved precsion of standard whitepoint chromaticities</li>
+	<li>Improved precision of standard whitepoint chromaticities</li>
 	<li>Removed a trademark from description of one predefined color space</li>
 	<li>Rephrased interpolation to be more generic wrt to interpolation space</li>
 	<li>Corrected Accessibility Considerations section</li>

css-color-5/Overview.bs

@@ -255,7 +255,7 @@ After normalizing both percentages, the result is produced via the following alg
 The result of mixing is the color at the specified percentage along the progression
 of the second color to the first color.
 
-Note: As a corrollary, a percentage of 0% just returns the other color converted to the specified color space,
+Note: As a corollary, a percentage of 0% just returns the other color converted to the specified color space,
 and a percentage of 100% returns the same color converted to the specified color space.
 
 <div class="example" id="ex-mix-lch-peru40">
@@ -272,7 +272,7 @@ and a percentage of 100% returns the same color converted to the specified color
 
 	<figure id="fig-LCH-peru-goldenrod">
 		<object data="images/CH-mixing.svg"  width=480 height=480>
-			<p>A mixture of two colours, and the mixed output.
+			<p>A mixture of two colors, and the mixed output.
 				We are looking down the CIE L axis onto the ab plane.
 				There are two axes, labelled <em>a</em> and <em>b</em>
 				which cross at the origin,
@@ -314,7 +314,7 @@ and a percentage of 100% returns the same color converted to the specified color
 
 	<figure id="fig-LCH-teal-olive">
 		<object data="images/CH-mixing3.svg"  width=500 height=500>
-			<p>A mixture of two colours, and the mixed output.
+			<p>A mixture of two colors, and the mixed output.
 				We are looking down the CIE L axis onto the ab plane.
 				There are two axes, labelled <em>a</em> and <em>b</em>
 				which cross at the origin,
@@ -823,7 +823,7 @@ or taken from the origin color
 	parsing/color-valid-relative-color.html
 </wpt>
 
-The precise details of each function's changes to accomodate [=relative colors=] are listed below,
+The precise details of each function's changes to accommodate [=relative colors=] are listed below,
 but they all follow a common structure:
 
 * An [=origin color=] can be specified with a ''from <<color>>'' value at the start of the function.
@@ -1459,7 +1459,7 @@ which is out of sRGB gamut,
 color(srgb -0.6018 0.7621 0.8448)
 as the negative red component indicates.
 Bring this into gamut
-by reducing Oklch Chroma, yeilds
+by reducing Oklch Chroma, yields
 <span class="swatch" style="--color: rgb(0.079% 69.282% 72.067%)"></span> oklch(0.69012 0.1173 199.893).
 The Oklch chroma has dropped from 0.251 to 0.117.
 </div>
@@ -2653,7 +2653,7 @@ even if explicitly specified.
 	<pre>color-mix(in oklab, teal 70%, peru 70%)</pre>
 	would be the string "color-mix(in oklab, teal 70%, peru 70%)"
 	because the fact that these normalize to 50% each
-	is only discoverfed after percentage normalization.
+	is only discovered after percentage normalization.
 </div>
 
 The serialization of the result of a ''color-mix()'' function
@@ -2962,7 +2962,7 @@ No new privacy considerations have been reported on this specification.
 <ul>
 	<!-- to 1 July 2023 -->
 	<li>Use reference ranges for percent to number conversions</li>
-	<li>Made ''hsl()'' and ''hwb()'' channel values number, per CSSSWG resolution. 
+	<li>Made ''hsl()'' and ''hwb()'' channel values number, per CSSWG resolution. 
 		Also made all the hue angle channel values number, in degrees. 
 		The RCS intro already said this but the change had not been fully propagated.</li>
 	<!-- to 28 June 2023 -->
@@ -3032,7 +3032,7 @@ No new privacy considerations have been reported on this specification.
 	<li>Clearly described potential clash of component names with named constants such as PI</li>
 	<li>Clarified that Relative Color Syntax does not use legacy (comma-separated) syntax</li>
 	<li>Corrected grammar of the rgb() function, ''none''' was not listed as an option for alpha</li>
-	<li>Changed serialization of color-mix() which uses hsl or hwb, to maximise precision</li>
+	<li>Changed serialization of color-mix() which uses hsl or hwb, to maximize precision</li>
 	<li>Added an out of gamut color-mix example</li>
 	<li>Use the term "cannot express the color" to describe HSL and HWB models which cannot represent extended, out of gamut colors.</li>
 	<li>Fixed some spelling errors</li>
@@ -3077,7 +3077,7 @@ No new privacy considerations have been reported on this specification.
 	<li>Clarified that the color-adjuster is not optional</li>
 	<li>Clarified that the percentage in color-mix is mandatory</li>
 	<li>Moved hue-adjuster back to color-mix whee it belongs</li>
-	<li>Added example with different mxing color spaces</li>
+	<li>Added example with different mixing color spaces</li>
 	<!-- to 27 Apr 2021 -->
 	<li>Added examples of percentage normalization in color-mix()</li>
 	<li>Explicitly excluded negative percentages in color-mix()</li>
@@ -3143,7 +3143,7 @@ No new privacy considerations have been reported on this specification.
 		</ol>
 
 		In addition the new ''color-mix()'' function allows two colors to be mixed,
-		in a specified color space, to yeild a new color.
+		in a specified color space, to yield a new color.
 
 
 		<wpt hidden title="CSS 2.1 or CSS Color 3 tests, not relevant for this level">
@@ -3437,7 +3437,7 @@ No new privacy considerations have been reported on this specification.
 			parsing/color-valid-lab.html
 			parsing/color-valid-rgb.html
 			parsing/color-valid-system-color.html
-			system-color-hightlights-vs-getSelection-001.html
+			system-color-highlights-vs-getSelection-001.html
 		</wpt>
 
 		<wpt hidden title="CSS Color 6">

css-conditional-3/Overview.bs

@@ -596,7 +596,7 @@ Instead, authors must write one of the following:
 </pre>
 </div>
 
-<wpt title="Parentheses are required to mix opeartors.">
+<wpt title="Parentheses are required to mix operators.">
 at-supports-016.html
 css-supports-013.xht
 css-supports-014.xht

css-conditional-4/Overview.bs

@@ -212,7 +212,7 @@ Additions since Level 3</h3>
 <wpt hidden title="CSS Conditional 5 tests">
 </wpt>
 
-<wpt hidden title="Untagged, probaly conditional 3, needs triage">
+<wpt hidden title="Untagged, probably conditional 3, needs triage">
 	at-media-whitespace-optional-001.html
 	at-media-whitespace-optional-002.html
 	at-supports-001.html

css-conditional-5/Overview.bs

@@ -46,7 +46,7 @@ Introduction</h2>
 	which generalizes the concept of a conditional rule.
 	Anything that can be expressed in an existing conditional rule
 	can be expressed in ''@when''
-	by wrappng it in an appropriate function
+	by wrapping it in an appropriate function
 	to declare what kind of condition it is.
 	This allow authors to easily combine multiple types of queries,
 	such as media queries and supports queries,
@@ -94,12 +94,12 @@ Extensions to the definition of support</h3>
 
 	A CSS processor is considered to
 	<dfn export for=CSS id="dfn-support-font-tech">support a font tech</dfn>
-	when it is capable of utilising the specified [[css-fonts-4#font-tech-definitions]]
+	when it is capable of utilizing the specified [[css-fonts-4#font-tech-definitions]]
 	in layout and rendering.
 
 	A CSS processor is considered to
 	<dfn export for=CSS id="dfn-support-font-format">support a font format</dfn>
-	when it is capable of utilising the specified [[css-fonts-4#font-format-definitions]]
+	when it is capable of utilizing the specified [[css-fonts-4#font-format-definitions]]
 	in layout and rendering,
 	and this format is not specified as a <<string>>.
 

css-conditional-5/font-tech-format-explainer.md

@@ -43,7 +43,7 @@ that have evolved over the years (
 [history](https://github.com/w3c/csswg-drafts/blob/main/css-fonts-4/src-explainer.md#history-of-font-technologies).
 So the file signature or mime type for font files is not sufficient to identify
 whether a UA's font stack would support it. Instead it is necessary to
-distinguish what text layout (OpenType, AAT, Graphite) or rasterisation
+distinguish what text layout (OpenType, AAT, Graphite) or rasterization
 technologies (TrueType contours, variations, bitmap color font formats, vector
 color font formats etc.) are used by the respective font file.
 
@@ -118,7 +118,7 @@ overrides is not needed.
 
 ```
 if (CSS.supports("font-tech(palettes)") {
-  // Load palette styleheet here.
+  // Load palette stylesheet here.
   if (CSS.supports("font-tech(color-COLRv1)")) {
     // Load COLRv1 font here.
   } else if (CSS.supports("font-tech(color-COLRv0)) {