The 'box-shadow' property attaches one or more drop-shadows to the box.
diff --git a/css-box-3/block-layout.bs b/css-box-3/block-layout.bs
index 5c3944edf90f..0ec193eec17a 100644
--- a/css-box-3/block-layout.bs
+++ b/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.
-
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.
diff --git a/css-cascade-4/Overview.bs b/css-cascade-4/Overview.bs
index 33d5cd736675..c667c2deb50f 100644
--- a/css-cascade-4/Overview.bs
+++ b/css-cascade-4/Overview.bs
@@ -1376,7 +1376,7 @@ Additions Since Level 3
* 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]].
@@ -2795,7 +2795,7 @@
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.
@page :right {
diff --git a/css-gcpm-3/2009-06-10.src.html b/css-gcpm-3/2009-06-10.src.html
index 8959112f7178..2af2aa50f74a 100644
--- a/css-gcpm-3/2009-06-10.src.html
+++ b/css-gcpm-3/2009-06-10.src.html
@@ -969,20 +969,20 @@ Footnote calls
-->
@@ -2058,7 +2058,7 @@ The ''pages'' counter
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.
@page :right {
diff --git a/css-gcpm-3/Overview.bs b/css-gcpm-3/Overview.bs
index a4d77da8e0fa..bad73bec744e 100644
--- a/css-gcpm-3/Overview.bs
+++ b/css-gcpm-3/Overview.bs
@@ -45,7 +45,7 @@ For readability they have not been repeated explicitly.
-[[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. Named strings copy text for reuse in margin boxes. Running elements 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. Named strings copy text for reuse in margin boxes. Running elements move elements (complete with style and structure) from the document to margin boxes.
Named strings
diff --git a/css-grid-3/Overview.bs b/css-grid-3/Overview.bs
index 3e2da5003d49..27e95979c0c8 100644
--- a/css-grid-3/Overview.bs
+++ b/css-grid-3/Overview.bs
@@ -118,7 +118,7 @@ Grid Item Placement
Grid items are placed using these steps:
- Place the items as if the [=masonry axis=] had ''grid-template-columns/none'' specified in that axis.
-
- 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.
+
- 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.
- Place items using the Masonry layout algorithm below.
diff --git a/css-highlight-api-1/Overview.bs b/css-highlight-api-1/Overview.bs
index ce5143fa7222..e8f3474d4daf 100644
--- a/css-highlight-api-1/Overview.bs
+++ b/css-highlight-api-1/Overview.bs
@@ -162,7 +162,7 @@ Creating Custom Highlights
The name of a [=custom highlight=]
is represented by its {{Highlight/name}} attribute,
- which must must be a valid <>.
+ which must be a valid <>.
<![CDATA[
[Exposed=Window]
diff --git a/css-images-3/Overview.bs b/css-images-3/Overview.bs
index 6a0b439e0f25..7ce157e6b6cf 100644
--- a/css-images-3/Overview.bs
+++ b/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
diff --git a/css-images-4/Overview.bs b/css-images-4/Overview.bs
index 579473bd450e..690827d7a506 100644
--- a/css-images-4/Overview.bs
+++ b/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=],
diff --git a/css-inline-3/Overview.bs b/css-inline-3/Overview.bs
index 06894440c894..33f69025f0c3 100644
--- a/css-inline-3/Overview.bs
+++ b/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.)
diff --git a/css-lists-3/Overview.bs b/css-lists-3/Overview.bs
index deab14f9b3d0..ece042bdaf4e 100644
--- a/css-lists-3/Overview.bs
+++ b/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>
diff --git a/css-multicol-1/Overview.bs b/css-multicol-1/Overview.bs
index d9e2fc07fe01..06c26bfa8d1f 100644
--- a/css-multicol-1/Overview.bs
+++ b/css-multicol-1/Overview.bs
@@ -1280,8 +1280,6 @@ Filling Columns</h2>
</dd>
</dl>
- Issue: We need to define the behavior of ''column-fill'' in continuous contexts. A previous resolution (<a href="https://github.com/w3c/csswg-drafts/issues/3224#issuecomment-468089503">3224</a>) defined that the property should only be consulted if the length of columns was constrained in the block dimension. This was reverted in (<a href="https://github.com/w3c/csswg-drafts/issues/4036#issuecomment-531646703">4036</a>) pending further discussion.
-
In continuous contexts, this property does not have any effect when there are overflow columns.
<div class="example">
@@ -1579,7 +1577,7 @@ This appendix is <em>informative</em>.
<li>Changed the value of normal for column-gap to be 1em, rather than a UA-specified length with a suggestion of 1em. <a href="https://github.com/w3c/csswg-drafts/issues/2145#issuecomment-378781507">Resolved: 4 Apr 2018</a></li>
<li>Clarified that negative values are not allowed for column-width, and that while 0 may be specified, used values will be clamped to a minimum of 1px. <a href="https://github.com/w3c/csswg-drafts/issues/1741#issuecomment-373091628">Resolved: 14 Mar 2018</a></li>
<li>Clarified that where there is a spanning element content is automatically balanced across all columns in the immediately preceding column row before the element appears. <a href="https://github.com/w3c/csswg-drafts/issues/1075">Resolved: 9 Nov 2017</a></li>
- <li>Added clarification plus an additional example that spanning elements may be lower the the first level of descendants, and that in the case of margins, borders and padding on the element containing the spanning, this would be drawn above the spanner. <a href="https://github.com/w3c/csswg-drafts/issues/1072#issuecomment-342668025">Resolved: 8 Nov 2017</a></li>
+ <li>Added clarification plus an additional example that spanning elements may be lower the first level of descendants, and that in the case of margins, borders and padding on the element containing the spanning, this would be drawn above the spanner. <a href="https://github.com/w3c/csswg-drafts/issues/1072#issuecomment-342668025">Resolved: 8 Nov 2017</a></li>
<li>Changed the sentence <q>Column rules are painted in the inline content layer, but below all inline content inside the multicol element.</q> to <q>Column rules are painted just above the border of the multicol element. For scrollable multicol elements, note that while the border and background of the multicol element obviously aren’t scrolled, the rules need to scroll along with the columns.</q> <a href="https://github.com/w3c/csswg-drafts/issues/1739#issuecomment-342659978">Resolved: 7 Nov 2017</a></li>
<li>Under section The Multi-column Model, removed two sentences <q>That is, column boxes behave like block-level, table cell, and inline-block boxes as per CSS 2.1, section 10.1, item 2 CSS21. However, column boxes do not establish block container boxes for elements with ''position: fixed or position: absolute''.</q>. These were replaced with a clarification about the principal box and a new example showing how abspos elements refer to the multicol container. <a href="https://github.com/w3c/csswg-drafts/issues/1738#issuecomment-342661881">Resolved: 7 Nov 2017</a></li>
<li>Removed the sentence "To indicate where column breaks should (or should not) appear, new keyword values are introduced." and following example (Example 7 in the WD published <a href="https://www.w3.org/TR/2017/WD-css-multicol-1-20171005/">5 Oct 2017</a>) as the multicol specification no longer introduces these properties. <a href="https://github.com/w3c/csswg-drafts/issues/1966">Editorial</a></li>
@@ -1591,7 +1589,7 @@ This appendix is <em>informative</em>.
<a href="https://www.w3.org/TR/2011/CR-css3-multicol-20110412/">Candidate Recommendation (CR) of 12 April 2011</a>.</h3>
<ul>
- <li>Added July 2016 resolution to change the the track size floor to a required UA-specified value, consistent with the CSS Grid spec. <a href="https://lists.w3.org/Archives/Public/www-style/2016Jan/0031.html">Resolved: 7 Jan 2016</a>
+ <li>Added July 2016 resolution to change the track size floor to a required UA-specified value, consistent with the CSS Grid spec. <a href="https://lists.w3.org/Archives/Public/www-style/2016Jan/0031.html">Resolved: 7 Jan 2016</a>
<li>Remove the restriction about overflow columns only being in continuous media in the statement that 'column-fill' has no effect on overflow columns. <a href="https://lists.w3.org/Archives/Public/www-style/2013Sep/0471.html">Resolved: September 2013</a>.
<li>Added keyword balance-all and examples to demonstrate how this should work. <a href="https://lists.w3.org/Archives/Public/www-style/2013Sep/0471.html">Resolved: September 2013</a>.
<li> The pseudo-algorithm has been revised on a number of occasions. <a href="https://lists.w3.org/Archives/Public/www-style/2013Feb/0471.html">Latest change Feb 2013</a>.
diff --git a/css-overscroll-1/Overview.bs b/css-overscroll-1/Overview.bs
index 72d8b56fa3fd..e063eb9a3fa5 100644
--- a/css-overscroll-1/Overview.bs
+++ b/css-overscroll-1/Overview.bs
@@ -123,7 +123,7 @@ potentially confusing rubber banding effect in addition to scroll chaining.
}
</pre>
-In this case the the author can use <a value for=overscroll-behavior>none</a> on the infinite
+In this case the author can use <a value for=overscroll-behavior>none</a> on the infinite
scroller to prevent both scroll chaining and overscroll affordance.
</div>
diff --git a/css-overscroll-1/README.md b/css-overscroll-1/README.md
index 734a2f371361..b6d44ebb4950 100644
--- a/css-overscroll-1/README.md
+++ b/css-overscroll-1/README.md
@@ -5,7 +5,7 @@ https://wicg.github.io/overscroll-behavior/
# Problem
-Scroll chaining is the process of propagating the scroll event to the the nearest scrollable parent element once a scrollable reaches its limit. Scroll chaining is not always desirable. For example, consider a fixed/absolute position scroller whose scroll should not chain to the parent scroller, i.e. the document. You can find this UX pattern used in most chat boxes that live at the bottom of a page such as in Facebook or GMail UIs.
+Scroll chaining is the process of propagating the scroll event to the nearest scrollable parent element once a scrollable reaches its limit. Scroll chaining is not always desirable. For example, consider a fixed/absolute position scroller whose scroll should not chain to the parent scroller, i.e. the document. You can find this UX pattern used in most chat boxes that live at the bottom of a page such as in Facebook or GMail UIs.
To give you a sense of how popular preventing scroll chaining may be, according to my quick http-archive search "-ms-scroll-chaining: none" is used in 0.4% of top 300K pages despite being limited in functionality and only supported on IE/Edge.
diff --git a/css-page-3/Overview.bs b/css-page-3/Overview.bs
index f23801f52ef5..2312387fa0e1 100644
--- a/css-page-3/Overview.bs
+++ b/css-page-3/Overview.bs
@@ -1756,7 +1756,7 @@ Page size: the 'size' property</h3>
<dd>
A page size can be specified using one of the following media names. This is
the equivalent of specifying 'size'
- using length values. The definition of the the media names comes from
+ using length values. The definition of the media names comes from
Media Standardized Names [[!PWGMSN]].
<dl dfn-type=value dfn-for="<page-size>">
diff --git a/css-page-floats-3/Overview.bs b/css-page-floats-3/Overview.bs
index 0102b0f70cbb..45aa04f4d75f 100644
--- a/css-page-floats-3/Overview.bs
+++ b/css-page-floats-3/Overview.bs
@@ -720,7 +720,7 @@ The 'clear' property</h2>
<p class="note">
Negative float-defer values put the initial float reference a certain number
to be a certain amount of fragmentation containers from the last fragmentation
- container at the time of of the placement. Subsequent page float stacking
+ container at the time of the placement. Subsequent page float stacking
can mean that a page float is being placed in a later fragmentation container
(a page float with float-defer set to -3 can end up being placed in the
last fragmentation container), and later page floats may mean that new
diff --git a/css-pseudo-4/Overview.bs b/css-pseudo-4/Overview.bs
index 4dbcdffc5724..ebf838119a68 100644
--- a/css-pseudo-4/Overview.bs
+++ b/css-pseudo-4/Overview.bs
@@ -641,7 +641,7 @@ Area of a Highlight</h3>
css/css-pseudo/active-selection-043.html
</wpt>
<li>
- The overlay may also include other other areas within the border-box of an element;
+ The overlay may also include other areas within the border-box of an element;
in this case, those areas belong to the innermost such element that contains the area.
<li>
For an [=inline-level box=], the overlay may extend outside its border edges
diff --git a/css-scoping-1/Overview.bs b/css-scoping-1/Overview.bs
index 4647890b2fa1..a8eee1b3051c 100644
--- a/css-scoping-1/Overview.bs
+++ b/css-scoping-1/Overview.bs
@@ -186,7 +186,7 @@ Matching Selectors Against Shadow Trees</h4>
<div class="example">
For example,
- any selector in a stylesheet embedded in or linked from an an element in a <a>shadow tree</a>
+ any selector in a stylesheet embedded in or linked from an element in a <a>shadow tree</a>
is <a>in the context of a shadow tree</a>.
So is the argument to {{querySelector()}} when called from a <a>shadow root</a>.
</div>
@@ -221,7 +221,7 @@ Selecting Shadow Hosts from within a Shadow Tree</h4>
It would not be very good if a component used a particular class name
internally in a <a>shadow tree</a> stylesheet,
and the page author using the component accidentally <em>also</em>
- used the the same class name and put it on the <a>shadow host</a>.
+ used the same class name and put it on the <a>shadow host</a>.
Such a situation would result in accidental styling
that is impossible for the component author to predict,
and confusing for the page author to debug.
@@ -310,7 +310,7 @@ Selecting Into the Light: the '':host'', '':host()'', and '':host-context()'' ps
<div class='example'>
For example, a group of components can define a handful of color themes
- they they know how to respond to.
+ they know how to respond to.
Page authors could opt into a particular theme
by adding a specific class to the components,
or higher up in the document.
diff --git a/css-speech-1/Overview.bs b/css-speech-1/Overview.bs
index a7c60dde34a1..f1742fbd0e5e 100644
--- a/css-speech-1/Overview.bs
+++ b/css-speech-1/Overview.bs
@@ -532,7 +532,7 @@ The 'speak-as' property</h3>
Spells the text one letter at a time (useful for acronyms and abbreviations).
In languages where accented characters are rare,
it is permitted to drop accents in favor of alternative unaccented spellings.
- As as example, in English, the word “rôle” can also be written as “role”.
+ As an example, in English, the word “rôle” can also be written as “role”.
A conforming implementation would thus be able to spell-out “rôle” as “R O L E”.
<dt><dfn>digits</dfn>
@@ -667,9 +667,9 @@ Collapsing pauses</h3>
provided the former has no 'rest-before' and no 'cue-before'.
<li>The 'pause-after' of an aural "box" and the 'pause-before' of its next sibling.
<li>The 'pause-before' and 'pause-after' of an aural "box",
- if the the "box" has a 'voice-duration' of "0ms"
+ if the "box" has a 'voice-duration' of "0ms"
and no 'rest-before' or 'rest-after' and no 'cue-before' or 'cue-after',
- or if the the "box" has no rendered content at all (see 'speak').
+ or if the "box" has no rendered content at all (see 'speak').
</ul>
A collapsed pause is considered adjoining to another pause
diff --git a/css-tables-3/Overview.bs b/css-tables-3/Overview.bs
index 3c9b40fef21e..77481919582d 100644
--- a/css-tables-3/Overview.bs
+++ b/css-tables-3/Overview.bs
@@ -951,7 +951,7 @@ spec:css-sizing-3; type:property; text:box-sizing
<li>The 'border-spacing' of the <a>table-root</a> is ignored (as if it was set to 0px).
<li>The 'border-radius' of both <a>table-root</a> and <a>table-non-root</a> boxes
- is ignored (as it it was set to 0px).
+ is ignored (as if it was set to 0px).
<li>The values used for the layout and rendering of the borders of the <a>table-root</a>
and the <a>table-cell</a> boxes it owns are
determined using a special conflict resolution algorithm described in [[#border-collapsing]].
diff --git a/css-template-1/Overview.html b/css-template-1/Overview.html
index 31eae66241fb..6ee369b39623 100644
--- a/css-template-1/Overview.html
+++ b/css-template-1/Overview.html
@@ -2080,7 +2080,7 @@ <h3 id=slot-sizes><span class=secno>3.7. </span>Calculating the size of the
contents of the column (i.e., the column widths are specified with only
<a href="#ltlengthgt"><var><length></var></a> values, ‘<code
class=css>*</code>’, <var><fraction></var> values, or any
- combination of those), then <a href="#minw"><var>MINW</var></a> is is
+ combination of those), then <a href="#minw"><var>MINW</var></a> is
the sum of the slot's left and right margin, border and paddding (i.e.,
any ‘<a href="#margin-left"><code
class=property>margin-left</code></a>’, ‘<a
diff --git a/css-template-1/Overview.src.html b/css-template-1/Overview.src.html
index 91afcb6c90cc..cea8981fc16e 100644
--- a/css-template-1/Overview.src.html
+++ b/css-template-1/Overview.src.html
@@ -1441,7 +1441,7 @@ <h3 id=slot-sizes>Calculating the size of the grid</h3>
contents of the column (i.e., the column widths are specified with
only <var><length></var> values, '*',
<var><fraction></var> values, or any combination of those), then
-<var>MINW</var> is is the sum of the slot's left and right margin,
+<var>MINW</var> is the sum of the slot's left and right margin,
border and paddding (i.e., any 'margin-left', 'margin-right',
'padding-left' etc., that is set on it by means of the
<span>'::slot()' pseudo-element</span>). Any ''auto'' margins are
diff --git a/css-template-1/new.html b/css-template-1/new.html
index a6e3d130c5bc..5599f51af10d 100644
--- a/css-template-1/new.html
+++ b/css-template-1/new.html
@@ -1179,7 +1179,7 @@ <h2 id=display><span class=secno>3. </span> Declaring a grid template</h2>
<p>Proposed text:
<p>An element is a <dfn id=grid-element1>grid element</dfn> (i.e., it
- defines a grid for its descendants) if it generates a a <a
+ defines a grid for its descendants) if it generates a <a
href="http://www.w3.org/TR/CSS21/visuren.html#block-boxes">block
container box</a> <a href="#CSS21"
rel=biblioentry>[CSS21]<!--{{!CSS21}}--></a> and one or more of the
@@ -3119,7 +3119,7 @@ <h3 id=alignment><span class=secno>6.1. </span> Alignment</h3>
<dt><dfn id=center>‘<code class=css>center</code>’</dfn>
<dd> Places the center of the <i>grid item</i>‘<code class=css>s
- margin box at the center of the the <i>grid item</i></code>’s
+ margin box at the center of the <i>grid item</i></code>’s
column.
<dt><dfn id=stretch>‘<code class=css>stretch</code>’</dfn>
@@ -3185,7 +3185,7 @@ <h3 id=alignment><span class=secno>6.1. </span> Alignment</h3>
<dt><dfn id=center0>‘<code class=css>center</code>’</dfn>
<dd> Places the center of the <i>grid item</i>‘<code class=css>s
- margin box at the center of the the <i>grid item</i></code>’s row.
+ margin box at the center of the <i>grid item</i></code>’s row.
<dt><dfn id=stretch0>‘<code class=css>stretch</code>’</dfn>
diff --git a/css-template-1/new.src.html b/css-template-1/new.src.html
index c5d000d9940c..fd86ee761a40 100644
--- a/css-template-1/new.src.html
+++ b/css-template-1/new.src.html
@@ -2523,7 +2523,7 @@ <h3 id=alignment>
<dt><dfn>''center''</dfn>
<dd>
Places the center of the <i>grid item</i>'s margin box at the
- center of the the <i>grid item</i>'s column.
+ center of the <i>grid item</i>'s column.
</dd>
<dt><dfn>''stretch''</dfn>
<dd>
@@ -2576,7 +2576,7 @@ <h3 id=alignment>
<dt><dfn>''center''</dfn>
<dd>
Places the center of the <i>grid item</i>'s margin box at the
- center of the the <i>grid item</i>'s row.
+ center of the <i>grid item</i>'s row.
</dd>
<dt><dfn>''stretch''</dfn>
<dd>
diff --git a/css-text-3/Overview.bs b/css-text-3/Overview.bs
index 3eeb73d4163b..eaf03d83cb00 100644
--- a/css-text-3/Overview.bs
+++ b/css-text-3/Overview.bs
@@ -1305,7 +1305,7 @@ Order of Operations</h4>
for representation in the DOM,
so when an HTML document is represented as a [[DOM]] tree
each line feed (U+000A)
- is treated as as a [=segment break=].
+ is treated as a [=segment break=].
Note: In most common CSS implementations,
HTML does not get styled directly.
@@ -3703,7 +3703,7 @@ Line Breaking Details</h3>
if the word contains a conditional hyphen (&shy; or U+00AD),
in favor of the conditional hyphen(s).
However, if, even after breaking at such opportunities,
- a portion of that word is is still too long to fit on one line,
+ a portion of that word is still too long to fit on one line,
an automatic hyphenation opportunity may be used.
<wpt pathprefix="/css/vendor-imports/mozilla/mozilla-central-reftests/text3/">
diff --git a/css-text-3/test-coverage.html b/css-text-3/test-coverage.html
index 8f6d3cc60f99..ff9ce9c6d966 100644
--- a/css-text-3/test-coverage.html
+++ b/css-text-3/test-coverage.html
@@ -43,7 +43,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="cont
and each section links to the corresponding one in he specification.
<div class=issue>Issue:
- <p>Problems other than missing spec coverage are highlighted he same as as this paragraph is.
+ <p>Problems other than missing spec coverage are highlighted the same as this paragraph is.
</div>
<hr>
@@ -266,7 +266,7 @@ <h3 id="hyphenation-the-hyphens-property">5.4 <a href="https://drafts.csswg.org/
<li>No test of Animation type.
<li>Affects intrinsic sizing
<li>Automatic hyphenation opportunities within a word must be ignored if the word contains a conditional hyphen (­ or U+00AD), in favor of the conditional hyphen(s)
- <li>However, if, even after breaking at such opportunities, a portion of that word is is still too long to fit on one line, an automatic hyphenation opportunity may be used.
+ <li>However, if, even after breaking at such opportunities, a portion of that word is still too long to fit on one line, an automatic hyphenation opportunity may be used.
</ul>
<h3 id="overflow-wrapping-the-overflow-wrapword-wrap-property">5.5 <a href="https://drafts.csswg.org/css-text-3/#overflow-wrap-property">Overflow Wrapping: the overflow-wrap/word-wrap property</a></h3>
diff --git a/css-text-4/Overview.bs b/css-text-4/Overview.bs
index 1a120d9e08dc..f89cc027af8a 100644
--- a/css-text-4/Overview.bs
+++ b/css-text-4/Overview.bs
@@ -232,7 +232,7 @@ Detecting Word Boundaries: the 'word-boundary-detection' property</h4>
Note: Wildcards <em>in the language subtag</em> would imply
support for detecting word boundaries in an undefined and effectively unlimited set of languages.
- As this this is not possible,
+ As this is not possible,
wildcards in the language subtag always result in the declaration
being treated as invalid.
@@ -1852,7 +1852,7 @@ Line Start/End Padding: the 'line-padding' property</h3>
an extra 0.5em of inline background will be visible
on each side of each line.
If it renders such that there is a break between “some” and “text”,
- the the additional padding will be:
+ the additional padding will be:
on the first line, black on the left and green on the right,
and on the second line, green on both sides.
diff --git a/css-text-decor-3/Overview.bs b/css-text-decor-3/Overview.bs
index 63abcbba2fbc..12822079339f 100644
--- a/css-text-decor-3/Overview.bs
+++ b/css-text-decor-3/Overview.bs
@@ -851,7 +851,7 @@ Text Shadows: the 'text-shadow' property</h2>
treating ''box-shadow/none'' as a zero-item list
and appending blank shadows (''transparent 0 0 0'')
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
</pre>
This property accepts a comma-separated list of shadow effects
diff --git a/css-text-decor-4/Overview.bs b/css-text-decor-4/Overview.bs
index 231643f385fc..10d30a9086ef 100644
--- a/css-text-decor-4/Overview.bs
+++ b/css-text-decor-4/Overview.bs
@@ -1928,7 +1928,7 @@ Text Shadows: the 'text-shadow' property</h2>
treating ''box-shadow/none'' as a zero-item list
and appending blank shadows (''transparent 0 0 0 0'')
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
</pre>
This property accepts a comma-separated list of shadow effects
diff --git a/css-transforms-2/Overview.bs b/css-transforms-2/Overview.bs
index e76a4a9cbdbb..eeb2eb640111 100644
--- a/css-transforms-2/Overview.bs
+++ b/css-transforms-2/Overview.bs
@@ -231,7 +231,7 @@ The transform is a 50° rotation about the vertical, Y axis. Note how this ma
### Perspective ### {#perspective}
-Perspective can be used to add a feeling of depth to a scene by making elements higher on the Z axis (closer to the viewer) appear larger, and those further away to appear smaller. The scaling is proportional to <var>d</var>/(<var>d</var> − <var>Z</var>) where <var>d</var>, the value of 'perspective', is the distance from the drawing plane to the the assumed position of the viewer's eye.
+Perspective can be used to add a feeling of depth to a scene by making elements higher on the Z axis (closer to the viewer) appear larger, and those further away to appear smaller. The scaling is proportional to <var>d</var>/(<var>d</var> − <var>Z</var>) where <var>d</var>, the value of 'perspective', is the distance from the drawing plane to the assumed position of the viewer's eye.
The appearance of perspective can be applied to a 3d-transformed element in two ways. First, the element's 'transform function list' can contain the ''perspective()'' function which computes into the element's 'current transformation matrix'.
@@ -315,7 +315,7 @@ The rendering of elements in a 3D rendering context is as follows (numbers refer
<ol style="list-style-type: upper-alpha;">
<li>The background, borders and other box decorations of the establishing element are rendered (steps 1 and 2)
- <li>The content and descendant elements without 3D transforms, ordered according to steps 3—7, are rendered into a plane at z=0 relative to to the establishing element.
+ <li>The content and descendant elements without 3D transforms, ordered according to steps 3—7, are rendered into a plane at z=0 relative to the establishing element.
<li>3D-transformed elements are each rendered into their own plane, transformed by the <a href="#accumulated-3d-transformation-matrix-computation">accumulated 3D transformation matrix</a>.
<li>Intersection is performed between the set of planes generated by steps B and C, according to <a href="http://en.wikipedia.org/wiki/Newell%27s_algorithm">Newell's algorithm</a>.
<li>The resulting set of planes is rendered on top of the backgrounds and box decorations rendered in this step A. Coplanar [=3D transformed elements=] are rendered in painting order.
diff --git a/css-transitions-1/Overview.bs b/css-transitions-1/Overview.bs
index a9e5ae2eeeee..c2861184985f 100644
--- a/css-transitions-1/Overview.bs
+++ b/css-transitions-1/Overview.bs
@@ -1057,7 +1057,7 @@ Completion of transitions {#complete}
<a>Running transitions</a>
<dfn export for="transition" id="dfn-complete">complete</dfn>
at a time that is equal to or after their end time,
- but prior to to the first <a>style change event</a>
+ but prior to the first <a>style change event</a>
whose time is equal to or after their <a>end time</a>.
When a transition completes,
implementations must move
diff --git a/css-ui-3/Overview.bs b/css-ui-3/Overview.bs
index ece305c1782b..24a332a164aa 100644
--- a/css-ui-3/Overview.bs
+++ b/css-ui-3/Overview.bs
@@ -1002,7 +1002,7 @@ The UA must support the following image file formats:
<li>SVG, as defined in [[!SVG11]], in <a href="https://www.w3.org/TR/SVG2/conform.html#secure-static-mode">secure static mode</a> [[!SVG2]], if it has a [=natural size=].
<li>any other non-animated image file format that they support
for <<image>> in other properties,
- such as the the 'background-image' property
+ such as the 'background-image' property
</ul>
In addition, the UA should support the following image file formats:
@@ -1010,7 +1010,7 @@ In addition, the UA should support the following image file formats:
<li>SVG, as defined in [[!SVG11]], in <a href="https://www.w3.org/TR/SVG2/conform.html#secure-animated-mode">secure animated mode</a> [[!SVG2]], if it has a [=natural size=].
<li>any other animated image file format that they support
for <<image>> in other properties,
- such as the the 'background-image' property
+ such as the 'background-image' property
</ul>
The UA may also support additional file formats, including SVG, as defined in [[!SVG11]], in secure static mode or secure animated mode [[!SVG2]], even if it does not have a [=natural size=].
diff --git a/css-ui-3/transition-cr-2017-11.md b/css-ui-3/transition-cr-2017-11.md
index e6cf6760cf0a..167baff3c770 100644
--- a/css-ui-3/transition-cr-2017-11.md
+++ b/css-ui-3/transition-cr-2017-11.md
@@ -36,7 +36,7 @@ There are 4 normative changes, all based on feedback from actual implementations
* Allow, but stop requiring support for SVG images without intrinsic sizes for cursors (corresponding test update).
* Align the spec with implementations, and make cursor: auto look like text over selectable text, and over editable elements (corresponding tests).
-The first 3 changes are are small tweaks and cannot make an implementation that conformed to the spec prior to the changes become non-conformant.
+The first 3 changes are small tweaks and cannot make an implementation that conformed to the spec prior to the changes become non-conformant.
The 4th change could theoretically impact conformance, but in practice does not.
Zero known implementations (Gecko/Edge/Webkit/Blink/Presto) conformed with the previous wording (the [issue 1598 was openly reviewed and discussed](https://github.com/w3c/csswg-drafts/issues/1598) for several months),
diff --git a/css-ui-3/transition-pr-2017-11.md b/css-ui-3/transition-pr-2017-11.md
index 933b4b07db0e..0091a45e4913 100644
--- a/css-ui-3/transition-pr-2017-11.md
+++ b/css-ui-3/transition-pr-2017-11.md
@@ -36,7 +36,7 @@ There are 4 normative changes, all based on feedback from actual implementations
* Allow, but stop requiring support for SVG images without intrinsic sizes for cursors (corresponding test update).
* Align the spec with implementations, and make cursor: auto look like text over selectable text, and over editable elements (corresponding tests).
-The first 3 changes are are small tweaks and cannot make an implementation that conformed to the spec prior to the changes become non-conformant.
+The first 3 changes are small tweaks and cannot make an implementation that conformed to the spec prior to the changes become non-conformant.
The 4th change could theoretically impact conformance, but in practice does not.
Zero known implementations (Gecko/Edge/Webkit/Blink/Presto) conformed with the previous wording (the [issue 1598 was openly reviewed and discussed](https://github.com/w3c/csswg-drafts/issues/1598) for several months),
diff --git a/css-ui-4/Overview.bs b/css-ui-4/Overview.bs
index fba45040751d..c3f18b8d9e97 100644
--- a/css-ui-4/Overview.bs
+++ b/css-ui-4/Overview.bs
@@ -664,7 +664,7 @@ Values have the following meanings:
<li>
any other non-animated image file format that they support
for <<image>> in other properties,
- such as the the 'background-image' property
+ such as the 'background-image' property
</ul>
In addition, the UA should support the following image file formats:
@@ -678,7 +678,7 @@ Values have the following meanings:
<li>
any other animated image file format that they support
for <<image>> in other properties,
- such as the the 'background-image' property
+ such as the 'background-image' property
</ul>
The UA may also support additional file formats,
diff --git a/css-variables-1/Overview.bs b/css-variables-1/Overview.bs
index 7ae8ba153222..295189b57774 100644
--- a/css-variables-1/Overview.bs
+++ b/css-variables-1/Overview.bs
@@ -347,7 +347,7 @@ Resolving Dependency Cycles</h3>
Both '--one' and '--two' are now [=cyclic at computed-value time=],
and compute to the [=guaranteed-invalid value=]
- rather than than lengths.
+ rather than lengths.
</div>
It is important to note that
diff --git a/css-writing-modes-4/Overview.bs b/css-writing-modes-4/Overview.bs
index 125ed76b0db7..b5da0d5b0dba 100644
--- a/css-writing-modes-4/Overview.bs
+++ b/css-writing-modes-4/Overview.bs
@@ -2769,7 +2769,7 @@ Full-width Characters</h5>
<!--
Also, a <a property>font-variant</a> value of ''full-width'' must be ignored in such cases:
whether applied via ''@font-face'' descriptor or property declaration,
- within the combined text this value does not not cause the UA to enable that font feature. [[!CSS3-FONTS]]
+ within the combined text this value does not cause the UA to enable that font feature. [[!CSS3-FONTS]]
http://lists.w3.org/Archives/Public/www-style/2013Sep/0091.html
-->
diff --git a/css2/Overview.bs b/css2/Overview.bs
index 6a5a54805891..63f7ae9320e0 100644
--- a/css2/Overview.bs
+++ b/css2/Overview.bs
@@ -10647,7 +10647,7 @@ which inserts nothing, but increments the quotation depth by one.
'counter-increment'
and 'counter-reset'. The
counters defined by these properties are used with the counter() and
-counters() functions of the the 'content' property.
+counters() functions of the 'content' property.
</p>
<xmp class="propdef">
diff --git a/cssom-view-1/Overview.bs b/cssom-view-1/Overview.bs
index bda18ad9fb31..5f40ab6cf4cf 100644
--- a/cssom-view-1/Overview.bs
+++ b/cssom-view-1/Overview.bs
@@ -393,7 +393,7 @@ To <dfn>scroll to the beginning of the document</dfn> for a document <var>docume
<ol>
<li>Let <var>viewport</var> be the <a>viewport</a> that is associated with <var>document</var>. <!-- This assumes that there is a viewport, since
it is only invoked when navigating -->
- <li>Let <var>position</var> be the the scroll position <var>viewport</var> would have by aligning the <a>beginning edges</a> of the
+ <li>Let <var>position</var> be the scroll position <var>viewport</var> would have by aligning the <a>beginning edges</a> of the
<a>scrolling area</a> with the <a>beginning edges</a> of <var>viewport</var>.
<li>If <var>position</var> is the same as <var>viewport</var>'s current scroll position, and <var>viewport</var> does not have an ongoing
<a>smooth scroll</a>, abort these steps.
diff --git a/mediaqueries-4/Overview.bs b/mediaqueries-4/Overview.bs
index c9cde0046341..b72d60ff869f 100644
--- a/mediaqueries-4/Overview.bs
+++ b/mediaqueries-4/Overview.bs
@@ -2062,7 +2062,7 @@ Appendix A: Deprecated Media Features</h2>
<p class="note">To query for the size of the viewport (or the page box
on page media), the '@media/width', '@media/height' and 'aspect-ratio' <a>media features</a>
should be used, rather than 'device-width', 'device-height' and
- 'device-aspect-ratio', which refer to the physical size of the the device
+ 'device-aspect-ratio', which refer to the physical size of the device
regardless of how much space is available for the document being laid out. The
device-* <a>media features</a> are also sometimes used as a proxy to detect
mobile devices. Instead, authors should use <a>media features</a> that better
diff --git a/mediaqueries-5/Overview.bs b/mediaqueries-5/Overview.bs
index 9f26ef9c8f7a..ed61715a84a2 100644
--- a/mediaqueries-5/Overview.bs
+++ b/mediaqueries-5/Overview.bs
@@ -3012,7 +3012,7 @@ Appendix A: Deprecated Media Features</h2>
<p class="note">To query for the size of the viewport (or the page box
on page media), the '@media/width', '@media/height' and 'aspect-ratio' <a>media features</a>
should be used, rather than 'device-width', 'device-height' and
- 'device-aspect-ratio', which refer to the physical size of the the device
+ 'device-aspect-ratio', which refer to the physical size of the device
regardless of how much space is available for the document being laid out. The
device-* <a>media features</a> are also sometimes used as a proxy to detect
mobile devices. Instead, authors should use <a>media features</a> that better
diff --git a/scroll-animations-1/EXPLAINER.md b/scroll-animations-1/EXPLAINER.md
index 92cbfb2e9fd4..6e88c767b3a5 100644
--- a/scroll-animations-1/EXPLAINER.md
+++ b/scroll-animations-1/EXPLAINER.md
@@ -54,7 +54,7 @@ These are a class of animation whose progress is driven by time but whose activa
triggered when scrolling past a certain position or into a given scroll range. These are also
common on the web but they don't suffer from main thread jank and synchronous scrolling lad in the
same way that scroll-linked animations do. This is becuase only their activation is tied to scroll
-position and and not their progress.
+position and not their progress.
However, we found that in the vast majority of cases where a web author would want to do this, they
would want to do it for a CSS transition (as opposed to a CSS animation). Unfortunately, it's not
diff --git a/selectors-4/Overview.bs b/selectors-4/Overview.bs
index 3f64b57d4be0..1a9f34a46c38 100644
--- a/selectors-4/Overview.bs
+++ b/selectors-4/Overview.bs
@@ -2123,7 +2123,7 @@ The Target Container Pseudo-class: '':target-within''</h3>
The Reference Element Pseudo-class: '':scope''</h3>
In some contexts, selectors can be matched with an explicit set of <dfn dfn export lt=":scope element">:scope elements</dfn>.
- This is is a (potentially empty) set of elements
+ This is a (potentially empty) set of elements
that provide a reference point for selectors to match against,
such as that specified by the <code>querySelector()</code> call in [[DOM]].
@@ -3720,7 +3720,7 @@ Match a Selector Against a Tree</h3>
<li>
Start with a list of <var>candidate elements</var>,
- which are the the <var>root elements</var>
+ which are the <var>root elements</var>
and all of their descendant elements,
sorted in <a>shadow-including tree order</a>,
unless otherwise specified.
diff --git a/web-animations-1/Overview.bs b/web-animations-1/Overview.bs
index 8f408d45fed9..9411396b51de 100644
--- a/web-animations-1/Overview.bs
+++ b/web-animations-1/Overview.bs
@@ -4198,7 +4198,7 @@ interface Animation : EventTarget {
As a result, setting the {{Animation/playbackRate}} for an in-flight
animation may cause it to jump.
- To set the the [=playback rate=] for an in-flight animation such that it
+ To set the [=playback rate=] for an in-flight animation such that it
smoothly updates, use the asynchronous {{updatePlaybackRate()}} method.
</div>
@@ -5529,7 +5529,7 @@ otherwise, using the following procedure:
applying the <a>IDL attribute name to animation property name</a>
algorithm to <var>property name</var>.
- 1. Add a property to to <var>keyframe output</var> with <var>normalized
+ 1. Add a property to <var>keyframe output</var> with <var>normalized
property name</var> as the property name, and <var>property values</var>
as the property value.
diff --git a/web-animations-2/Overview.bs b/web-animations-2/Overview.bs
index 58a1cca0aefe..56bb64266003 100644
--- a/web-animations-2/Overview.bs
+++ b/web-animations-2/Overview.bs
@@ -1410,7 +1410,7 @@ With regards to repetition, this means the children operate
<em>inside</em> an iteration of the parent.
For example, if a <a>group effect</a> has an <a>iteration
-count</a> of 2, then the children of of the group will all play twice
+count</a> of 2, then the children of the group will all play twice
since they effectively play <em>inside</em> the group's iterations.
<figure>
@@ -1691,7 +1691,7 @@ after the step to apply the keyframe effect composite mode.
returned. When performing iteration composition on propreties
that do not support accumulation, the result should be the
initial property value of <var>target property</var> on
- <var>keyframe</var>, hence we we make this
+ <var>keyframe</var>, hence we make this
<var>V</var><sub>b</sub> in the above step.
<h3 id="combining-effects">Combining effects</h3>
]]>