From b554cf504ba7331b4b8eeae9b9d1c232dfa171c3 Mon Sep 17 00:00:00 2001 From: Nick Schonning Date: Mon, 22 Feb 2021 02:26:51 -0500 Subject: [PATCH] fix: typos across specs (#5992) --- biblio.ref | 2 +- css-2015/Overview.bs | 2 +- css-2020/Overview.bs | 2 +- css-animations-2/Overview.bs | 4 +- css-backgrounds-3/box-shadow.src.html | 2 +- css-backgrounds-3/issues-lc-2010.html | 2 +- css-backgrounds-3/issues-lc-2010.txt | 2 +- css-backgrounds-3/issues-lc-2012.txt | 2 +- .../transition-updated-cr-2017-09.md | 2 +- css-block-3/README | 2 +- css-box-3/block-layout.bs | 10 ++--- css-break-3/issues-cr-2016.bsi | 2 +- css-break-3/issues-cr-2016.html | 2 +- css-cascade-3/issues-cr-2016.bsi | 2 +- css-cascade-3/issues-cr-2016.html | 2 +- css-cascade-4/Overview.bs | 4 +- css-cascade-5/Overview.bs | 4 +- css-color-3/issues-lc-2008.html | 4 +- css-color-3/transition-cr-2017.md | 4 +- css-color-4/Overview.bs | 40 +++++++++---------- css-color-4/images/macbeth-naive.svg | 2 +- css-color-4/images/macbeth-pdfium.svg | 2 +- css-color-4/images/macbeth-roundtrip.svg | 2 +- css-color-5/Overview.bs | 6 +-- css-color-adjust-1/Overview.bs | 2 +- css-color-hdr/Overview.bs | 6 +-- css-conditional-3/Overview.bs | 2 +- css-conditional-values-1/Overview.bs | 2 +- css-contain-1/Overview.bs | 8 ++-- .../implementation-report-2019-09.html | 2 +- css-contain-1/issues-2017-cr.html | 12 +++--- css-contain-1/issues-2017-cr.txt | 12 +++--- css-contain-1/issues-2017.html | 6 +-- css-contain-1/issues-2017.txt | 10 ++--- css-contain-1/issues-2018-cr.html | 2 +- css-contain-1/issues-2018-cr.txt | 2 +- css-contain-2/Overview.bs | 4 +- css-counter-styles-3/Overview.bs | 2 +- css-device-adapt-1/Overview.bs | 4 +- css-display-3/issues-wd-2017.bsi | 10 ++--- css-display-3/issues-wd-2017.html | 10 ++--- css-egg-1/Overview.bs | 2 +- css-env-1/Overview.bs | 2 +- css-exclusions-1/Exclusions.src.html | 8 ++-- css-exclusions-1/Overview.bs | 2 +- .../processing-model-example-block-boxes.svg | 2 +- .../processing-model-example-layout-tree.svg | 2 +- .../images/processing-model-example.graffle | 8 ++-- css-flexbox-1/Overview.bs | 2 +- css-flexbox-1/issues-cr-20160526.bsi | 4 +- css-flexbox-1/issues-cr-20160526.html | 4 +- css-flexbox-1/issues-cr-2018.bsi | 4 +- css-flexbox-1/issues-cr-2018.html | 4 +- .../transition-updated-cr-2017-09.md | 2 +- css-fonts-3/Fonts.html | 12 +++--- css-fonts-3/Fonts.src.html | 10 ++--- css-fonts-3/Overview-wip.bs | 18 ++++----- css-fonts-3/Overview.html | 10 ++--- css-fonts-3/doc-20130711-LCWD.html | 2 +- css-fonts-3/transition-cr-2017.md | 2 +- css-fonts-4/Overview.bs | 10 ++--- css-gcpm-3/2009-06-10.html | 18 ++++----- css-gcpm-3/2009-06-10.src.html | 16 ++++---- css-gcpm-3/uc.html | 10 ++--- css-grid-1/issues-cr-2016.bsi | 10 ++--- css-grid-1/issues-cr-2016.html | 10 ++--- css-grid-1/issues-cr-2017.bsi | 8 ++-- css-grid-1/issues-cr-2017.html | 8 ++-- css-grid-1/issues-wd-20150917.bsi | 2 +- css-grid-1/issues-wd-20150917.html | 2 +- css-grid-1/issues-wd-20160519.bsi | 2 +- css-grid-1/issues-wd-20160519.html | 2 +- css-grid-3/Overview.bs | 4 +- css-highlight-api-1/Overview.bs | 2 +- css-images-3/issues-cr-2012.html | 2 +- css-images-3/issues-cr-2012.json | 2 +- css-images-3/issues-cr-2012.txt | 2 +- css-images-3/issues-cr-2012.yaml | 2 +- css-images-4/Overview.bs | 2 +- css-inline-3/Overview.bs | 4 +- css-logical-1/Overview.bs | 2 +- css-multicol-1/issues-2011.html | 2 +- css-multicol-1/issues-2011.txt | 2 +- css-multicol-1/issues-dec-2020.txt | 2 +- css-multicol-1/issues.html | 2 +- css-multicol-1/last-call.html | 2 +- css-namespaces-3/issues-1.txt | 2 +- css-overflow-3/Overview.bs | 20 +++++----- css-overflow-4/Overview.bs | 8 ++-- css-overscroll-1/README.md | 2 +- css-page-3/Overview.bs | 4 +- css-page-template-1/Overview.html | 2 +- css-page-template-1/Overview.src.html | 2 +- css-position-3/Overview.bs | 6 +-- css-pseudo-4/Overview.bs | 6 +-- css-regions-1/Overview.bs | 2 +- css-rhythm-1/Overview.bs | 2 +- css-round-display-1/Overview.bs | 2 +- css-ruby-1/Overview.bs | 8 ++-- css-scoping-1/deferred-to-level-4.txt | 2 +- css-scroll-snap-1/Overview.bs | 14 +++---- css-scroll-snap-1/diff-notes.html | 4 +- css-scroll-snap-1/diff.html | 4 +- css-scroll-snap-1/issues-2015-12.html | 4 +- css-scroll-snap-1/issues-2015-12.txt | 4 +- css-scroll-snap-1/issues-by-email.txt | 4 +- css-scroll-snap-1/issues-by-issue.html | 6 +-- css-scroll-snap-1/issues-by-issue.txt | 6 +-- css-shapes-1/split/notes | 2 +- css-shapes-2/Overview.bs | 6 +-- css-size-adjust-1/Overview.bs | 2 +- css-sizing-3/Overview.bs | 4 +- css-sizing-4/Overview.bs | 6 +-- css-speech-1/Overview.bs | 4 +- css-syntax-3/Overview.bs | 4 +- css-tables-3/Overview.bs | 30 +++++++------- css-template-1/Overview.html | 8 ++-- css-template-1/Overview.src.html | 10 ++--- css-template-1/new2.html | 2 +- css-template-1/new2.src.html | 2 +- css-text-3/Overview.bs | 18 ++++----- css-text-3/test-coverage.html | 6 +-- css-text-4/Overview.bs | 12 +++--- css-text-decor-4/Overview.bs | 4 +- css-transforms-1/ChangeLog | 16 ++++---- css-transforms-1/Overview.bs | 4 +- css-transforms-1/issues-wd-2013.html | 2 +- css-transforms-1/issues-wd-2013.txt | 2 +- css-transforms-1/test/Overview.html | 4 +- css-transforms-2/Overview.bs | 6 +-- css-transitions-1/use-cases.html | 4 +- css-ui-3/Overview.bs | 4 +- css-ui-3/implementation-report.html | 2 +- css-ui-3/issues-2012-2015.html | 4 +- css-ui-3/issues-2012-2015.txt | 4 +- css-ui-3/transition-cr-2017-11.md | 4 +- css-ui-3/transition-pr-2017-11.md | 4 +- css-ui-4/Overview.bs | 12 +++--- css-ui-4/issues-fpwd-2015.html | 2 +- css-ui-4/issues-fpwd-2015.txt | 2 +- css-writing-modes-3/Overview.bs | 6 +-- .../implementation-report-2019-08.html | 2 +- css-writing-modes-3/issues-cr-2015.html | 2 +- css-writing-modes-3/issues-cr-2015.txt | 2 +- css-writing-modes-3/issues-cr-2018.html | 6 +-- css-writing-modes-3/issues-cr-2018.txt | 6 +-- css-writing-modes-4/Overview.bs | 2 +- css2/Overview.bs | 2 +- css3-tables-algorithms/Overview.src.htm | 20 +++++----- mediaqueries-3/disposition.html | 6 +-- mediaqueries-3/disposition2.html | 2 +- mediaqueries-4/Overview.bs | 2 +- mediaqueries-4/issues-cr-2017-09-05.html | 10 ++--- mediaqueries-4/issues-cr-2017-09-05.txt | 10 ++--- mediaqueries-5/Overview.bs | 2 +- resize-observer-1/examples/chat.html | 4 +- resize-observer-1/explainer.md | 4 +- scroll-animations-1/EXPLAINER.md | 4 +- scroll-animations-1/Use cases.md | 2 +- selectors-3/Overview.html | 2 +- selectors-3/Overview.src.html | 4 +- selectors-4/Overview.bs | 8 ++-- selectors-4/deferred-for-level-5 | 2 +- shared/transition-templates/cr-updated.md | 2 +- shared/transition-templates/pr.md | 2 +- web-animations-1/Overview.bs | 10 ++--- web-animations-2/Overview.bs | 14 +++---- web-animations-2/img/time-calculations.svg | 2 +- 168 files changed, 442 insertions(+), 442 deletions(-) diff --git a/biblio.ref b/biblio.ref index 4276abff55f..aa2d8459fc2 100644 --- a/biblio.ref +++ b/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 diff --git a/css-2015/Overview.bs b/css-2015/Overview.bs index 9451dc71b53..4572459b30f 100644 --- a/css-2015/Overview.bs +++ b/css-2015/Overview.bs @@ -107,7 +107,7 @@ Background: The W3C Process and CSS
Recommendation (REC)
- 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. diff --git a/css-2020/Overview.bs b/css-2020/Overview.bs index f29878b3574..22021fb9179 100644 --- a/css-2020/Overview.bs +++ b/css-2020/Overview.bs @@ -318,7 +318,7 @@ Fairly Stable Modules with limited implementation experience [[!CSS-COLOR-4]]
Extends and supersedes [[CSS-COLOR-3]], - further expanding the range of colors expressable in CSS. + further expanding the range of colors expressible in CSS.
CSS Display Module Level 3 [[CSS-DISPLAY-3]] diff --git a/css-animations-2/Overview.bs b/css-animations-2/Overview.bs index 68d6f80f2ee..93c95a670d4 100644 --- a/css-animations-2/Overview.bs +++ b/css-animations-2/Overview.bs @@ -83,7 +83,7 @@ with the additions here into a complete level 2 specification.

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.
For example, the following stylesheet defines two different animations - targetting the 'scale' property. + targeting the 'scale' property. 
     @keyframes heartbeat {
diff --git a/css-backgrounds-3/box-shadow.src.html b/css-backgrounds-3/box-shadow.src.html
index edaa9674716..cc47c0fdd19 100644
--- a/css-backgrounds-3/box-shadow.src.html
+++ b/css-backgrounds-3/box-shadow.src.html
@@ -55,7 +55,7 @@ 
Abstract

 
 
Status of this document

 
-
This is a scrappy bit of an Editor'd Draft, is totally unstable,
+
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.

 
diff --git a/css-backgrounds-3/issues-lc-2010.html b/css-backgrounds-3/issues-lc-2010.html
index ac8a64f9902..e4cfff773aa 100644
--- a/css-backgrounds-3/issues-lc-2010.html
+++ b/css-backgrounds-3/issues-lc-2010.html
@@ -123,7 +123,7 @@ 
CSS Backgrounds and Borders Level 3 Disposition of Comments

 
 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
diff --git a/css-backgrounds-3/issues-lc-2010.txt b/css-backgrounds-3/issues-lc-2010.txt
index 7f261eae1e8..e3fa0d01f94 100644
--- a/css-backgrounds-3/issues-lc-2010.txt
+++ b/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
diff --git a/css-backgrounds-3/issues-lc-2012.txt b/css-backgrounds-3/issues-lc-2012.txt
index d6e27a5fa24..17808b26ff3 100644
--- a/css-backgrounds-3/issues-lc-2012.txt
+++ b/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
diff --git a/css-backgrounds-3/transition-updated-cr-2017-09.md b/css-backgrounds-3/transition-updated-cr-2017-09.md
index a41d07ecfda..bf746021d0a 100644
--- a/css-backgrounds-3/transition-updated-cr-2017-09.md
+++ b/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
 
diff --git a/css-block-3/README b/css-block-3/README
index f776fe360e9..26e33eaa4d2 100644
--- a/css-block-3/README
+++ b/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
diff --git a/css-box-3/block-layout.bs b/css-box-3/block-layout.bs
index 0ec193eec17..f2d68aa370f 100644
--- a/css-box-3/block-layout.bs
+++ b/css-box-3/block-layout.bs
@@ -1272,7 +1272,7 @@ depending on the percentages was undefined in CSS level 2.
 
 

 
Some UAs implementing CSS level 2 try to solve the set of linear
-equations when containing-block is unkown:
+equations when containing-block is unknown:
 

 
margin + width = containing-block

 margin = percentage × containing-block
@@ -1405,7 +1405,7 @@ area or border area (depending on
   properties. See Calculating widths, heights
   and margins below.
 
-  
complex 
(Only on 'height'.) The same as ''heght/auto'', except
+  
complex 
(Only on 'height'.) The same as ''height/auto'', except
   that elements with a complex aspect ratio (defined below) are
   considered to
   have an intrinsic ratio. More precisely: for the purposes
@@ -1977,7 +1977,7 @@ to be known in order to calculate the used height, or vice versa,
   
  • 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.
 
   
  • 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,
   
  • 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.
 
   
  • 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.”
 
- 
    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
diff --git a/css-break-3/issues-cr-2016.bsi b/css-break-3/issues-cr-2016.bsi
index 5823b9641d8..65c418b094c 100644
--- a/css-break-3/issues-cr-2016.bsi
+++ b/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
diff --git a/css-break-3/issues-cr-2016.html b/css-break-3/issues-cr-2016.html
index b0ace41417f..d15e4f09981 100644
--- a/css-break-3/issues-cr-2016.html
+++ b/css-break-3/issues-cr-2016.html
@@ -101,7 +101,7 @@ 
    CSS Fragmentation Module Level 3 Disposition of Comments for 2016-01-14 CRResponse: 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
diff --git a/css-cascade-3/issues-cr-2016.bsi b/css-cascade-3/issues-cr-2016.bsi
index cbd8aabc632..5efa2006707 100644
--- a/css-cascade-3/issues-cr-2016.bsi
+++ b/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.
diff --git a/css-cascade-3/issues-cr-2016.html b/css-cascade-3/issues-cr-2016.html
index e14fc4bb8b6..eda798143b2 100644
--- a/css-cascade-3/issues-cr-2016.html
+++ b/css-cascade-3/issues-cr-2016.html
@@ -48,7 +48,7 @@ 
    CSS Cascading and Inheritance Module Level 3 Disposition of Comments for 201
 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. #
diff --git a/css-cascade-4/Overview.bs b/css-cascade-4/Overview.bs
index c667c2deb50..f60c6923889 100644
--- a/css-cascade-4/Overview.bs
+++ b/css-cascade-4/Overview.bs
@@ -88,7 +88,7 @@ Module Interactions
 	For the purpose of this specification,
 	text nodes are treated as element 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 defaulting.
 
 
+	
 
 	To naively convert from RGBA to CMYK:
 
@@ -4348,7 +4348,7 @@ Transparency: the 'opacity' property
 
 	
    
 		overlapping glphs rendered correctly, and incorrectly
+		alt="overlapping glyphs rendered correctly, and incorrectly">
 		
    
 			Correct and incorrect rendering of text
 			with an 'opacity' value of less than one,
@@ -4792,14 +4792,14 @@ Changes
 	
  • Consistent minimum precision between lab() and color(lab)
    • 
 
 	
-	
  • Clarified fallback procedure for the color() function – first valid in-gamut color, else first valid color which is then gamut maped, else transparent black
    • 
-	
  • Clarified difference betwen opacity property and colors with opacity, notably for rendering overlapping text glyphs
    • 
+	
  • Clarified fallback procedure for the color() function – first valid in-gamut color, else first valid color which is then gamut mapped, else transparent black
    • 
+	
  • Clarified difference between opacity property and colors with opacity, notably for rendering overlapping text glyphs
    • 
 	
  • Added sample (but verified correct) code for ΔE2000
    • 
-	
  • Added definitin of previously-undefined term chromaticity, with examples; define chromaticity diagram.
    • 
+	
  • Added definition of previously-undefined term chromaticity, with examples; define chromaticity diagram.
    • 
 	
  • Added explanation of color additivity, with examples
    • 
 	
  • Added source links to WPT tests
    • 
 	
  • Export definition of color, and valid color, for other specifications to reference
    • 
-	
  • Define minimum nuber of bits per component, for serialization
    • 
+	
  • Define minimum number of bits per component, for serialization
    • 
 	
  • Updated "applies to" definitions (CSS-wide change)
    • 
 	
  • Added image state (display referred or scene referred) for predefined colorspaces
    • 
 	
  • Listed white point correlated color temperature (e.g. D65) alongside chromaticity coordinates, for clarity
    • 
@@ -4817,7 +4817,7 @@ Changes
 	
  • Update requirement from WCAG 2.0 to 2.1
    • 
 	
  • Fully specify Unicode characters used for serialization
    • 
 	
  • Define serialization of special named colors
    • 
-	
  • Define serializatin of ''device-cmyk()''
    • 
+	
  • Define serialization of ''device-cmyk()''
    • 
 	
  • Define serialization of ''color()''
    • 
 	
  • Fully define RGB serialization, in maximally web-compatible way
    • 
 	
  • Define serialization of Lab and LCH
    • 
@@ -4830,17 +4830,17 @@ Changes
 	
  • Clarify out-of-range clamping
    • 
 	
  • Add examples of specified values
    • 
 	
  • Clarify computed values
    • 
-	
  • Resst fingerprinting, with mandatory mappings for deprecated system colors
    • 
+	
  • Resist fingerprinting, with mandatory mappings for deprecated system colors
    • 
 	
 	
  • Added explanatory note on history and reason for standardizing X11 colors
    • 
 	
  • Correct hwb sample code
    • 
 	
  • Add table of DeltaE2000 values for MacBeth patches
    • 
-	
  • Add note on ICC profe Internet Media type
    • 
+	
  • Add note on ICC profile Internet Media type
    • 
 	
  • Add reference to PNG sRGB chunk
    • 
 	
  • Clarify CMYK to Lab interconversion
    • 
 	
  • Clarify RGB to Lab interconversion
    • 
 	
  • More comparison of HSL vs. LCH
    • 
-	
  • More descripton for Rec BT.2020 colorspace
    • 
+	
  • More description for Rec BT.2020 colorspace
    • 
 	
  • Updated description of prophoto-rgb
    • 
 	
  • Removed duplicate "keywords" from Value Definitions section 
    • 
 	
  • Added an example of an invalid color
    • 
@@ -4850,7 +4850,7 @@ Changes
 	
  • Clarify some examples and explanatory notes
    • 
 	
  • Handling for valid and invalid ICC profiles
    • 
 	
  • Define handling for images with explicit tagged colorspace
    • 
-	
  • Define clorspace for 4k, SDR video
    • 
+	
  • Define colorspace for 4k, SDR video
    • 
 	
  • State that user contrast settings mst take precedence
    • 
 	
  • Clarify meaning of system colors outside for forced-color mode
    • 
 	
  • Update default style rules
    • 
@@ -4995,7 +4995,7 @@ this risk is believed to be mitigated.
 This specification adds to CSS the on-demand
 downloading of ICC profiles.
 These do not contain executable code,
-and thus do not consitiute an increased security risk.
+and thus do not constitute an increased security risk.
 
 
 Accessibility Considerations {#a11y-sec}
diff --git a/css-color-4/images/macbeth-naive.svg b/css-color-4/images/macbeth-naive.svg
index 489d3e3f333..08396de7704 100644
--- a/css-color-4/images/macbeth-naive.svg
+++ b/css-color-4/images/macbeth-naive.svg
@@ -4,7 +4,7 @@ Rectangular patches are sRGB, converted from averaged measured Lab values.
 Circles show same Lab values, converted to CMYK
 with an ICC profile
 for premium coated paper, tac 300% and medium GCR
-with the FOGRA51 characterisation set.
+with the FOGRA51 characterization set.
 CMYK values then "naively" converted to sRGB.
 Note: the cyan patch has has the LCH Chroma reduced,
 to bring it inside the sRGB gamut.
diff --git a/css-color-4/images/macbeth-pdfium.svg b/css-color-4/images/macbeth-pdfium.svg
index c3ae18d4a07..cedb4e8e53a 100644
--- a/css-color-4/images/macbeth-pdfium.svg
+++ b/css-color-4/images/macbeth-pdfium.svg
@@ -3,7 +3,7 @@
 Rectangular patches are sRGB, converted from averaged measured Lab values.
 Circles show same Lab values, converted to CMYK
 with an ICC profile
-with the FOGRA39 characterisation set.
+with the FOGRA39 characterization set.
 CMYK values then coverted to sRGB
 with the
 Note: the cyan patch has has the LCH Chroma reduced,
diff --git a/css-color-4/images/macbeth-roundtrip.svg b/css-color-4/images/macbeth-roundtrip.svg
index b35ea957799..aac7c3156ec 100644
--- a/css-color-4/images/macbeth-roundtrip.svg
+++ b/css-color-4/images/macbeth-roundtrip.svg
@@ -4,7 +4,7 @@ Rectangular patches are sRGB, converted from averaged measured Lab values.
 Circles show same Lab values, converted to CMYK
 with an ICC profile
 for premium coated paper, tac 300% and medium GCR
-with the FOGRA51 characterisation set.
+with the FOGRA51 characterization set.
 CMYK values then coverted back to Lab
 with the same profile (round-trip) and then converted to sRGB.
 Note: the cyan patch has has the LCH Chroma reduced,
diff --git a/css-color-5/Overview.bs b/css-color-5/Overview.bs
index 6686c248c5b..a831d424ab3 100644
--- a/css-color-5/Overview.bs
+++ b/css-color-5/Overview.bs
@@ -85,7 +85,7 @@ In some cases, the result of physically mixing two colored lights is desired
 (in that case, the CIE XYZ colorspace is appropriate, because it is linear in light intensity).
 In other cases, colors which are evenly spaced perceptually are desired
 (in which case, the CIE Lab colorspace is designed to be perceptually uniform).
-Alternatively, maximising chroma so that color mixtures follow along the hue wheel is wanted
+Alternatively, maximizing chroma so that color mixtures follow along the hue wheel is wanted
 (CIE LCH works well for this).
 Lastly, compatibility with legacy Web content may be the most important consideration.
 (the sRGB colorspace, which is neither linear-light nor perceptually uniform, is the choice here).
@@ -437,7 +437,7 @@ which is rgb(52.446% 45.821% 62.953%)
 	The lightness of the red is left unchanged.
 
 	This shows a desaturated result, compared to LCH interpolation,
-	because interpolation is in a stright line on the a,b plane
+	because interpolation is in a straight line on the a,b plane
 	and can thus pass close to the central, neutral axis.
 
 	
    color-mix(lab rgb(82.02% 30.21% 35.02%) a 38% b 38%, rgb(5.64% 55.94% 85.31%));
    
@@ -685,7 +685,7 @@ When an origin color is present, the following keywords can also be used in this
 	* ''lab(from var(--mycolor) l a b / calc(alpha - 20%))'' reduces the alpha of ''var(--mycolor)'' by 20% of 100%.
 
 	Note that all the adjustments are lossless in the sense that no gamut clipping occurs, since lab() encompasses all visible color.
-	This is not true for the alpha adjustments in the sRGB based functions (such as'rgb()', 'hsl()', or 'hwb()'), which would also convert to sRGB in addition to adjusting the alpha transparency.
+	This is not true for the alpha adjustments in the sRGB based functions (such as 'rgb()', 'hsl()', or 'hwb()'), which would also convert to sRGB in addition to adjusting the alpha transparency.
    diff --git a/css-color-adjust-1/Overview.bs b/css-color-adjust-1/Overview.bs index 52f68c8994a..4de93576fab 100644 --- a/css-color-adjust-1/Overview.bs +++ b/css-color-adjust-1/Overview.bs @@ -322,7 +322,7 @@ Forced Color Schemes {#forced} when '@media/forced-colors' is ''active'', reducing effects such as shadows, fades, blurs, filters, gradients, and image or pattern fills - that add complexity to discerning shape outlin + that add complexity to discerning shape outline --> Properties Affected by Forced Colors Mode {#forced-colors-properties} diff --git a/css-color-hdr/Overview.bs b/css-color-hdr/Overview.bs index 66ef718e1c5..86f9cd5e92a 100644 --- a/css-color-hdr/Overview.bs +++ b/css-color-hdr/Overview.bs @@ -104,7 +104,7 @@ Predefined colorspaces for HDR: {#predefined-HDR} colorspaces defined by CSS Color 4, the following HDR colorspaces are defined for use in the color function [[css-color-4#color-function]]. - Serialization of values in these new colorspaces is identical to the decription in [[css-color-4#serializing-color-values]]. + Serialization of values in these new colorspaces is identical to the description in [[css-color-4#serializing-color-values]]. rec2100-pq {#valdef-color-rec2100-pq} --------------------------- @@ -189,7 +189,7 @@ Predefined colorspaces for HDR: {#predefined-HDR} Issue: add other examples, including encoding of sRGB red, green, blue and P3 red, green, blue. - Linear-light RGB signals are converted to PQ encoded as follows. An absolute luminance scale is used, so the luminance of diffuse (media) white is required to scale relative luminances. The maximum encodable value (peak, small-area white) in PQ is 10,000 cd/m². Media whte is 203 cd/m² [[!Rpt_BT.2408]]. + Linear-light RGB signals are converted to PQ encoded as follows. An absolute luminance scale is used, so the luminance of diffuse (media) white is required to scale relative luminances. The maximum encodable value (peak, small-area white) in PQ is 10,000 cd/m². Media white is 203 cd/m² [[!Rpt_BT.2408]]. content-visibility/content-visibility-001.html @@ -1448,7 +1448,7 @@ Restrictions and Clarifications {#cv-notes} This is true even if both the root and the target elements are in the [=skipped contents=]. -2. From the perpsective of a {{ResizeObserver}}, +2. From the perspective of a {{ResizeObserver}}, the [=skipped contents=] of an element never change their size. If these elements become non-skipped later, diff --git a/css-counter-styles-3/Overview.bs b/css-counter-styles-3/Overview.bs index f0f1b7d5691..7d6e8ae0021 100644 --- a/css-counter-styles-3/Overview.bs +++ b/css-counter-styles-3/Overview.bs @@ -2503,7 +2503,7 @@ Additional Predefined Counter Styles

    APIs

    -

    +

    Extensions to the CSSRule interface

    The CSSRule interface is extended as follows: diff --git a/css-device-adapt-1/Overview.bs b/css-device-adapt-1/Overview.bs index 6f4598eb482..6dedc096a5c 100644 --- a/css-device-adapt-1/Overview.bs +++ b/css-device-adapt-1/Overview.bs @@ -183,8 +183,8 @@ computed 'direction' for the root element. browser? (And what's a desktop browser)". Need to say that a "desktop" browser typically have no UA styles, as opposed to the UA stylesheet outlined for current mobile -behaviour, and that no UA styles for ''@viewport'' will give "desktop" -behaviour per default (actual viewport is initial viewport).

    +behavior, and that no UA styles for ''@viewport'' will give "desktop" +behavior per default (actual viewport is initial viewport).

    diff --git a/css-display-3/issues-wd-2017.bsi b/css-display-3/issues-wd-2017.bsi index 457529c0bd7..269bc153788 100644 --- a/css-display-3/issues-wd-2017.bsi +++ b/css-display-3/issues-wd-2017.bsi @@ -187,7 +187,7 @@ Summary: Block containers can also establish an inline formatting context From: Oriol Comment: https://github.com/w3c/csswg-drafts/issues/1185 Response: https://github.com/w3c/csswg-drafts/issues/1185#issuecomment-301622704 -Cloed: Accepted +Closed: Accepted Resolved: Bugfix Comment: https://github.com/w3c/csswg-drafts/issues/1185#issuecomment-301630234 Response: https://github.com/w3c/csswg-drafts/issues/1185#issuecomment-314583112 @@ -212,7 +212,7 @@ Closed: Accepted Resolved: Bugfix ---- Issue 26. -Summary: Table contins invalid values +Summary: Table contains invalid values From: Oriol Comment: https://github.com/w3c/csswg-drafts/issues/1225 Response: https://github.com/w3c/csswg-drafts/issues/1225#issuecomment-301631015 @@ -454,7 +454,7 @@ Closed: Accepted Resolved: Editorial ---- Issue 53. -Summary: Discrepencies in run-in +Summary: Discrepancies in run-in From: Oriol Comment: https://github.com/w3c/csswg-drafts/issues/1491 Response: https://github.com/w3c/csswg-drafts/issues/1491#issuecomment-314570280 @@ -814,7 +814,7 @@ From: Amelia Bellamy-Royds Comment: https://github.com/w3c/csswg-drafts/issues/2502 Response: https://github.com/w3c/csswg-drafts/issues/2502#issuecomment-378809174 Closed: Accepted -Veified: https://github.com/w3c/csswg-drafts/issues/2502#issuecomment-399498551 +Verified: https://github.com/w3c/csswg-drafts/issues/2502#issuecomment-399498551 ---- Issue 96. Summary: Integrate definition of Shadow Trees @@ -833,7 +833,7 @@ Closed: Invalid Issue 98. Summary: Swap where default inner/outer display types are defined From: Oriol -Commment: https://github.com/w3c/csswg-drafts/issues/2658 +Comment: https://github.com/w3c/csswg-drafts/issues/2658 Response: https://github.com/w3c/csswg-drafts/issues/2658#issuecomment-391175246 Closed: Rejected Verified: https://github.com/w3c/csswg-drafts/issues/2658#issuecomment-393271657 diff --git a/css-display-3/issues-wd-2017.html b/css-display-3/issues-wd-2017.html index 60be88cb5ea..7f478f64378 100644 --- a/css-display-3/issues-wd-2017.html +++ b/css-display-3/issues-wd-2017.html @@ -227,7 +227,7 @@

    CSS Display Module Level 3 Disposition of Comments for 2015-10-15 WD

    From: Oriol Comment: https://github.com/w3c/csswg-drafts/issues/1185 Response: https://github.com/w3c/csswg-drafts/issues/1185#issuecomment-301622704 -Cloed: Accepted +Closed: Accepted Resolved: Bugfix Comment: https://github.com/w3c/csswg-drafts/issues/1185#issuecomment-301630234 Response: https://github.com/w3c/csswg-drafts/issues/1185#issuecomment-314583112 @@ -252,7 +252,7 @@

    CSS Display Module Level 3 Disposition of Comments for 2015-10-15 WD

    Resolved: Bugfix 
     Issue 26. #
-Summary:  Table contins invalid values
+Summary:  Table contains invalid values
 From:     Oriol
 Comment:  https://github.com/w3c/csswg-drafts/issues/1225
 Response: https://github.com/w3c/csswg-drafts/issues/1225#issuecomment-301631015
@@ -494,7 +494,7 @@ 
    CSS Display Module Level 3 Disposition of Comments for 2015-10-15 WD
    
 Resolved: Editorial
     Issue 53. #
-Summary:  Discrepencies in run-in
+Summary:  Discrepancies in run-in
 From:     Oriol
 Comment:  https://github.com/w3c/csswg-drafts/issues/1491
 Response: https://github.com/w3c/csswg-drafts/issues/1491#issuecomment-314570280
@@ -854,7 +854,7 @@ 
    CSS Display Module Level 3 Disposition of Comments for 2015-10-15 WD
    
 Comment:  https://github.com/w3c/csswg-drafts/issues/2502
 Response: https://github.com/w3c/csswg-drafts/issues/2502#issuecomment-378809174
 Closed:   Accepted
-Veified:  https://github.com/w3c/csswg-drafts/issues/2502#issuecomment-399498551
    +Verified: https://github.com/w3c/csswg-drafts/issues/2502#issuecomment-399498551 
     Issue 96. #
 Summary:  Integrate definition of Shadow Trees
@@ -873,7 +873,7 @@ 
    CSS Display Module Level 3 Disposition of Comments for 2015-10-15 WD
    
 Issue 98. #
 Summary:  Swap where default inner/outer display types are defined
 From:     Oriol
-Commment: https://github.com/w3c/csswg-drafts/issues/2658
+Comment:  https://github.com/w3c/csswg-drafts/issues/2658
 Response: https://github.com/w3c/csswg-drafts/issues/2658#issuecomment-391175246
 Closed:   Rejected
 Verified: https://github.com/w3c/csswg-drafts/issues/2658#issuecomment-393271657
diff --git a/css-egg-1/Overview.bs b/css-egg-1/Overview.bs
index c0cd19ca509..559c0c9e796 100644
--- a/css-egg-1/Overview.bs
+++ b/css-egg-1/Overview.bs
@@ -435,7 +435,7 @@ Double Rainbow
 
 <> allows sophisticated visual effects,
 but they are tedious to write, review and maintain
-as non trivial gradients cannot easily be visualised by merely reading the source.
+as non trivial gradients cannot easily be visualized by merely reading the source.
 This specification introduces a new syntax to describe a particular kind of <>: double rainbows.
 This spectacular visual effect which would improve most web pages
 is currently underused due to the difficulty of specifying it correctly.
diff --git a/css-env-1/Overview.bs b/css-env-1/Overview.bs
index e472d740e88..57036fd4ea3 100644
--- a/css-env-1/Overview.bs
+++ b/css-env-1/Overview.bs
@@ -25,7 +25,7 @@ capable of being substituted into arbitrary other properties via the ''var()'' f
 
 This specification defines a related, but simpler, concept of [=environment variables=].
 Unlike "cascading variables",
-which can change thruout the page as their corresponding [=custom property=] takes on different values,
+which can change throughout the page as their corresponding [=custom property=] takes on different values,
 an [=environment variable=] is "global" to a particular document--
 its value is the same everywhere.
 The ''env()'' function can then be used to substitute the value into arbitrary locations,
diff --git a/css-exclusions-1/Exclusions.src.html b/css-exclusions-1/Exclusions.src.html
index 12e7c325017..d895b7bb97b 100644
--- a/css-exclusions-1/Exclusions.src.html
+++ b/css-exclusions-1/Exclusions.src.html
@@ -360,7 +360,7 @@ 
    The 'wrap-flow' property
    
         computed to 'both', 'start', 'end' and 'clear' respectively. 
         The lighter gray areas show the additional areas 
         that are excluded for inline layout 
-        as a result of the 'wrap-flow'value. 
+        as a result of the 'wrap-flow' value. 
         For example, the area to the right of 'B' 
         cannot be used for inline layout 
         of left-to-right writing mode content 
@@ -1821,7 +1821,7 @@ 
    The 'shape-margin' property
    
 
     
    
         
    A 'shape-margin' creating an offset 
-            from a circlular shape-outside. 
+            from a circular shape-outside. 
             The blue rectangles represent 
             inline content affected 
             by the shape created 
@@ -1830,7 +1830,7 @@ 
    The 'shape-margin' property
    
             alt="Example of a shape-margin offset"/>
     
    
 
-    
+    
 
     
    The 'shape-padding' Property
    
     
    
@@ -1872,7 +1872,7 @@ 
    The 'shape-padding' Property
    
 
     
    
         
    A 'shape-padding' creating an offset 
-            from a circlular shape-inside. 
+            from a circular shape-inside. 
             The light blue rectangles represent 
             inline content affected 
             by the shape created 
diff --git a/css-exclusions-1/Overview.bs b/css-exclusions-1/Overview.bs
index cc653f41d74..0f9981e81c6 100644
--- a/css-exclusions-1/Overview.bs
+++ b/css-exclusions-1/Overview.bs
@@ -224,7 +224,7 @@ The 'wrap-flow' property
   represent exclusions in the element's wrapping context.
   A, B, C and D have their respective 'wrap-flow' computed to ''both'', ''start'',
   ''end'' and ''clear'' respectively. The lighter gray areas show the additional areas
-  that are excluded for inline layout as a result of the 'wrap-flow'value.
+  that are excluded for inline layout as a result of the 'wrap-flow' value.
   For example, the area to the right of B cannot be used for inline layout
   of left-to-right writing mode content because the 'wrap-flow' for B is ''start''.
 
diff --git a/css-exclusions-1/images/processing-model-example-block-boxes.svg b/css-exclusions-1/images/processing-model-example-block-boxes.svg
index 8edfdc2c5f7..0491e6b4d02 100644
--- a/css-exclusions-1/images/processing-model-example-block-boxes.svg
+++ b/css-exclusions-1/images/processing-model-example-block-boxes.svg
@@ -1,3 +1,3 @@
 
 
-2012-02-09 10:32ZCanvas 1blocks blocksICB (intial containing block)html-blockbody-blockd1-blockd2-blocke1-blocke2-block
+2012-02-09 10:32ZCanvas 1blocks blocksICB (initial containing block)html-blockbody-blockd1-blockd2-blocke1-blocke2-block
diff --git a/css-exclusions-1/images/processing-model-example-layout-tree.svg b/css-exclusions-1/images/processing-model-example-layout-tree.svg
index 7f1d61cdae6..d4fe7ba2287 100644
--- a/css-exclusions-1/images/processing-model-example-layout-tree.svg
+++ b/css-exclusions-1/images/processing-model-example-layout-tree.svg
@@ -1,3 +1,3 @@
 
 
-2012-04-15 20:29ZCanvas 1wrapping contextsICB (intial containing block)html-boxbody-boxd1-boxd2-boxe1-boxe2-box
+2012-04-15 20:29ZCanvas 1wrapping contextsICB (initial containing block)html-boxbody-boxd1-boxd2-boxe1-boxe2-box
diff --git a/css-exclusions-1/images/processing-model-example.graffle b/css-exclusions-1/images/processing-model-example.graffle
index 0869c4b89ef..249976188cb 100644
--- a/css-exclusions-1/images/processing-model-example.graffle
+++ b/css-exclusions-1/images/processing-model-example.graffle
@@ -769,7 +769,7 @@
 {\colortbl;\red255\green255\blue255;}
 \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural
 
-\f0\i\fs14 \cf0 ICB (intial containing block)}
+\f0\i\fs14 \cf0 ICB (initial containing block)}
 				VerticalPad
 				0
 			
@@ -1516,7 +1516,7 @@
 {\colortbl;\red255\green255\blue255;}
 \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural
 
-\f0\i\fs14 \cf0 ICB (intial containing block)}
+\f0\i\fs14 \cf0 ICB (initial containing block)}
 				VerticalPad
 				0
 			
@@ -2650,7 +2650,7 @@
 {\colortbl;\red255\green255\blue255;}
 \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural
 
-\f0\i\fs14 \cf0 ICB (intial containing block)}
+\f0\i\fs14 \cf0 ICB (initial containing block)}
 				VerticalPad
 				0
 			
@@ -3211,7 +3211,7 @@
 {\colortbl;\red255\green255\blue255;}
 \pard\tx560\tx1120\tx1680\tx2240\tx2800\tx3360\tx3920\tx4480\tx5040\tx5600\tx6160\tx6720\pardirnatural
 
-\f0\i\fs14 \cf0 ICB (intial containing block)}
+\f0\i\fs14 \cf0 ICB (initial containing block)}
 				VerticalPad
 				0
 			
diff --git a/css-flexbox-1/Overview.bs b/css-flexbox-1/Overview.bs
index 80bdfb65d0a..ab90c8c66ac 100644
--- a/css-flexbox-1/Overview.bs
+++ b/css-flexbox-1/Overview.bs
@@ -895,7 +895,7 @@ Collapsed Items
 			    display: flex;
 			    flex-flow: column;
 			  }
-			  /* dynamically collapse submenus when not targetted */
+			  /* dynamically collapse submenus when not targeted */
 			  nav > ul > li:not(:target):not(:hover) > ul {
 			    visibility: collapse;
 			  }
diff --git a/css-flexbox-1/issues-cr-20160526.bsi b/css-flexbox-1/issues-cr-20160526.bsi
index 92bc548117e..74a0c7dc352 100644
--- a/css-flexbox-1/issues-cr-20160526.bsi
+++ b/css-flexbox-1/issues-cr-20160526.bsi
@@ -5,7 +5,7 @@ Issues:   https://github.com/w3c/csswg-drafts/labels/css-flexbox-1
 
 ----
 Issue 1.
-Summary:  Scrollable oveflow vs alignment
+Summary:  Scrollable overflow vs alignment
 From:     Christian Biesinger
 Comment:  https://lists.w3.org/Archives/Public/www-style/2016May/0107.html
 Response: https://lists.w3.org/Archives/Public/www-style/2016Jun/0109.html
@@ -145,7 +145,7 @@ From:     fantasai
 Comment:  https://github.com/w3c/csswg-drafts/issues/316
 Closed:   Accepted
 Resolved: https://lists.w3.org/Archives/Public/www-style/2017Aug/0036.html
-Veified:  Reporter is editor
+Verified: Reporter is editor
 ----
 Issue 16A.
 Summary:  Baselines of empty boxes and other cases of baseline synthesis
diff --git a/css-flexbox-1/issues-cr-20160526.html b/css-flexbox-1/issues-cr-20160526.html
index 42acf6f3035..fbf2314b531 100644
--- a/css-flexbox-1/issues-cr-20160526.html
+++ b/css-flexbox-1/issues-cr-20160526.html
@@ -43,7 +43,7 @@ 
    CSS Flexible Box Layout Disposition of Comments for 2016-05-26 CR
    
 Verified indicates commentor's acceptance of the response.
    
 
     Issue 1. #
-Summary:  Scrollable oveflow vs alignment
+Summary:  Scrollable overflow vs alignment
 From:     Christian Biesinger
 Comment:  https://lists.w3.org/Archives/Public/www-style/2016May/0107.html ∈
 Response: https://lists.w3.org/Archives/Public/www-style/2016Jun/0109.html ∈
@@ -183,7 +183,7 @@ 
    CSS Flexible Box Layout Disposition of Comments for 2016-05-26 CR
    
 Comment:  https://github.com/w3c/csswg-drafts/issues/316
 Closed:   Accepted
 Resolved: https://lists.w3.org/Archives/Public/www-style/2017Aug/0036.html ∈
-Veified:  Reporter is editor
    
+Verified: Reporter is editor
     Issue 16A. #
 Summary:  Baselines of empty boxes and other cases of baseline synthesis
diff --git a/css-flexbox-1/issues-cr-2018.bsi b/css-flexbox-1/issues-cr-2018.bsi
index 433dead106f..086f9a8d142 100644
--- a/css-flexbox-1/issues-cr-2018.bsi
+++ b/css-flexbox-1/issues-cr-2018.bsi
@@ -101,7 +101,7 @@ Resolved: https://lists.w3.org/Archives/Public/www-style/2019Nov/0009.html
 Verified: https://github.com/w3c/csswg-drafts/issues/4065#issuecomment-553319697
 ----
 Issue 13.
-Summary:  ICB clamping of orthogonal flows shoud apply to flex container itself
+Summary:  ICB clamping of orthogonal flows should apply to flex container itself
 From:     Tab Atkins
 Comment:  https://github.com/w3c/csswg-drafts/issues/4221
 Open
@@ -131,7 +131,7 @@ Comment:  https://github.com/w3c/csswg-drafts/issues/4311
 Open
 ----
 Issue 18.
-Summary:  Do unresolable percentages prevent stretching?
+Summary:  Do unresolvable percentages prevent stretching?
 From:     Christian Biesinger
 Comment:  https://github.com/w3c/csswg-drafts/issues/4312
 Response: https://github.com/w3c/csswg-drafts/issues/4312#issuecomment-531981125
diff --git a/css-flexbox-1/issues-cr-2018.html b/css-flexbox-1/issues-cr-2018.html
index 31f0ac312bf..247d0ad2da8 100644
--- a/css-flexbox-1/issues-cr-2018.html
+++ b/css-flexbox-1/issues-cr-2018.html
@@ -141,7 +141,7 @@ 
    CSS Flexible Box Module Level 1 Disposition of Comments for 2018-11-19 CRVerified: https://github.com/w3c/csswg-drafts/issues/4065#issuecomment-553319697
     Issue 13. #
-Summary:  ICB clamping of orthogonal flows shoud apply to flex container itself
+Summary:  ICB clamping of orthogonal flows should apply to flex container itself
 From:     Tab Atkins
 Comment:  https://github.com/w3c/csswg-drafts/issues/4221
 Open
    @@ -171,7 +171,7 @@

    CSS Flexible Box Module Level 1 Disposition of Comments for 2018-11-19 CROpen 
     Issue 18. #
-Summary:  Do unresolable percentages prevent stretching?
+Summary:  Do unresolvable percentages prevent stretching?
 From:     Christian Biesinger
 Comment:  https://github.com/w3c/csswg-drafts/issues/4312
 Response: https://github.com/w3c/csswg-drafts/issues/4312#issuecomment-531981125
diff --git a/css-flexbox-1/transition-updated-cr-2017-09.md b/css-flexbox-1/transition-updated-cr-2017-09.md
index 1dd8c493888..7f375315ec2 100644
--- a/css-flexbox-1/transition-updated-cr-2017-09.md
+++ b/css-flexbox-1/transition-updated-cr-2017-09.md
@@ -8,7 +8,7 @@ CSS Flexible Box Layout Module Level 1
 
 https://drafts.csswg.org/css-flexbox/
 
-First Tuesday or Thursday after a sucessful transition decision
+First Tuesday or Thursday after a successful transition decision
 
 ## The document Abstract and Status sections
 
diff --git a/css-fonts-3/Fonts.html b/css-fonts-3/Fonts.html
index f776011f0f8..ef62f5d0e05 100644
--- a/css-fonts-3/Fonts.html
+++ b/css-fonts-3/Fonts.html
@@ -3370,7 +3370,7 @@ 
    5.3. Cluster matching
    
       single character and the font supports that character, select this font for
       the sequence and use the glyph associated with the canonically
-      equiavlent character for the entire cluster.
+      equivalent character for the entire cluster.
     
 
    
  • If no font was found in the font list in step 1:
@@ -4246,7 +4246,7 @@ 
    6.6. Capitalization:

    • -

    Quotes rendered italicised, with small-caps on the first line: +

    Quotes rendered italicized, with small-caps on the first line: 

    blockquote            { font-style: italic; }
 blockquote:first-line { font-variant: small-caps; }
@@ -4583,7 +4583,7 @@ 
    6.8. East
    used in some contexts. The exact set of characters and glyph forms will
    vary to some degree by context for which a given font was designed.
 
-  
    tradtional form example
    
+  
    traditional form example
    
 
   
    
    
    full-width
@@ -4703,7 +4703,7 @@ 
    6.9. Overall shorthand
    title="normal!!font-variant">‘normal’ resets all subproperties of ‘font-variant’ to their inital value. The font-variant’ to their initial value. The ‘none’ value sets ‘7.3. Feature
 
 
    If available, a Japanese font "Hiragino Maru Gothic" will be used.  When text
 rendering occurs, Japanese kana will be proportionally spaced and Latin text will
-be italicised.  Text rendered with the fallback serif font will use default
+be italicized.  Text rendered with the fallback serif font will use default
 rendering properties.
    --> diff --git a/css-fonts-3/Fonts.src.html b/css-fonts-3/Fonts.src.html index 3150c366721..5199754489a 100644 --- a/css-fonts-3/Fonts.src.html +++ b/css-fonts-3/Fonts.src.html @@ -2547,7 +2547,7 @@

    Cluster matching

  • If a sequence of multiple codepoints is canonically equivalent to a single character and the font supports that character, select this font for the sequence and use the glyph - associated with the canonically equiavlent character for the + associated with the canonically equivalent character for the entire cluster.
    • @@ -3216,7 +3216,7 @@

    Capitalization: the using all-small-caps in acronym-laden text

    Using small capitals to improve readability in acronym-laden text

    -

    Quotes rendered italicised, with small-caps on the first line:

    +

    Quotes rendered italicized, with small-caps on the first line:

    blockquote            { font-style: italic; }
 blockquote:first-line { font-variant: small-caps; }
@@ -3452,7 +3452,7 @@ 
    East Asian text rendering: the tradtional form example
    +
    traditional form example
    full-width
    Enables rendering of full-width variants (OpenType feature: fwid).
    @@ -3529,7 +3529,7 @@

    Overall shorthand for font rendering: the 'font-variant' property is a shorthand for all font-variant subproperties. -The value 'normal' resets all subproperties of 'font-variant' to their inital +The value 'normal' resets all subproperties of 'font-variant' to their initial value. The 'none' value sets 'font-variant-ligatures' to 'none' and resets all other font feature properties to their initial value. Like other shorthands, using 'font-variant' resets unspecified 'font-variant' subproperties to their initial @@ -3801,7 +3801,7 @@

    Feature precedence examples

    If available, a Japanese font "Hiragino Maru Gothic" will be used. When text rendering occurs, Japanese kana will be proportionally spaced and Latin text will -be italicised. Text rendered with the fallback serif font will use default +be italicized. Text rendered with the fallback serif font will use default rendering properties.

    --> diff --git a/css-fonts-3/Overview-wip.bs b/css-fonts-3/Overview-wip.bs index 32b47c55e5e..66b975a59ae 100644 --- a/css-fonts-3/Overview-wip.bs +++ b/css-fonts-3/Overview-wip.bs @@ -636,7 +636,7 @@ Initial: normal Applies to: all elements Inherited: yes Percentages: n/a -Computed value: as specifed +Computed value: as specified Animatable: no @@ -2157,7 +2157,7 @@ a base character, b and a sequence of combining characters 2. If a sequence of multiple codepoints is canonically equivalent to a single character and the font     supports that character, select this font for the sequence and use the glyph - associated with the canonically equiavlent character for the + associated with the canonically equivalent character for the entire cluster. 2. If no font was found in the font list in step 1: @@ -2680,7 +2680,7 @@ appears in all uppercase letters.
    using all-small-caps in acronym-laden text

    Using small capitals to improve readability in acronym-laden text

    - Quotes rendered italicised, with small-caps on the first line: + Quotes rendered italicized, with small-caps on the first line: 
     	blockquote            { font-style: italic; }
@@ -3012,7 +3012,7 @@ CSS user identifiers and are case-sensitive. They are unique only for
 a given set of font families and feature type.
 The same identifier used with a different feature type
 is treated as a separate and distinct value.  If the same identifier is defined
-mulitple times for a given feature type and font family,
+multiple times for a given feature type and font family,
 the last defined value is used. Values associated
 with a given identifier are <feature-index>es and are limited to integer values 0 or greater.
 
@@ -3278,7 +3278,7 @@ Individual values have the following meanings:
 		for which the older, traditional form is still used in some
 		contexts.  The exact set of characters and glyph forms will vary
 		to some degree by context for which a given font was designed.
-		
    tradtional form example
    
+		
    traditional form example
    
 
 	
    full-width
 	
    Enables rendering of full-width variants (OpenType feature: fwid).
@@ -3316,7 +3316,7 @@ Value: ]
    The 'font-variant' property is a shorthand for all 'font-variant-*' subproperties. -The value normal resets all subproperties of 'font-variant' to their inital +The value normal resets all subproperties of 'font-variant' to their initial value. The none value sets 'font-variant-ligatures' to ''font-variant-ligatures/none'' and resets all other font feature properties to their initial value. Like other shorthands, using 'font-variant' resets unspecified 'font-variant' subproperties to their initial @@ -3636,7 +3636,7 @@ feature except where explicitly defined for specific properties. If available, a Japanese font "Hiragino Maru Gothic" will be used. When text rendering occurs, Japanese kana will be proportionally spaced and Latin text will - be italicised. Text rendered with the fallback serif font will use default + be italicized. Text rendered with the fallback serif font will use default rendering properties.
    @@ -3692,7 +3692,7 @@ interface CSSFontFaceRule : CSSRule { }; -The DOM Level 2 Style specification [[DOM-LEVEL-2-STYLE]] defined a different variant of this rule. This definition supercedes that one. +The DOM Level 2 Style specification [[DOM-LEVEL-2-STYLE]] defined a different variant of this rule. This definition supersedes that one.

    The {{CSSFontFeatureValuesRule}} interface

    @@ -3799,7 +3799,7 @@ data. Specifically, font family name data is handled differently across platforms. For TrueType and OpenType fonts these names are contained -in the "name" table, in name records with name ID 1. Mulitple names +in the "name" table, in name records with name ID 1. Multiple names can be stored for different locales, but Microsoft recommends fonts always include at least a US English version of the name. On Windows, Microsoft made the decision for backwards compatibility to limit this diff --git a/css-fonts-3/Overview.html b/css-fonts-3/Overview.html index 57a5eba2ac3..c9a88fc5d5a 100755 --- a/css-fonts-3/Overview.html +++ b/css-fonts-3/Overview.html @@ -3370,7 +3370,7 @@

    5.3. Cluster matching

    single character and the font supports that character, select this font for the sequence and use the glyph associated with the canonically - equiavlent character for the entire cluster. + equivalent character for the entire cluster.
  • If no font was found in the font list in step 1: @@ -4246,7 +4246,7 @@

    6.6. Capitalization:
    -

    Quotes rendered italicised, with small-caps on the first line: +

    Quotes rendered italicized, with small-caps on the first line: 

    blockquote            { font-style: italic; }
 blockquote:first-line { font-variant: small-caps; }
@@ -4583,7 +4583,7 @@ 
    6.8. East
    used in some contexts. The exact set of characters and glyph forms will
    vary to some degree by context for which a given font was designed.
 
-  
    tradtional form example
    
+  
    traditional form example
    
 
   
    
    
    full-width
@@ -5041,7 +5041,7 @@ 
    7.3. Feature
 
 
    If available, a Japanese font "Hiragino Maru Gothic" will be used.  When text
 rendering occurs, Japanese kana will be proportionally spaced and Latin text will
-be italicised.  Text rendered with the fallback serif font will use default
+be italicized.  Text rendered with the fallback serif font will use default
 rendering properties.
    --> diff --git a/css-fonts-3/doc-20130711-LCWD.html b/css-fonts-3/doc-20130711-LCWD.html index 9af84d12b5a..02be2edfa5c 100644 --- a/css-fonts-3/doc-20130711-LCWD.html +++ b/css-fonts-3/doc-20130711-LCWD.html @@ -218,7 +218,7 @@

    CSS Fonts Module Level 3 Disposition of Comments for 2013-07-11 LCWD

    I18N Issue 292 http://lists.w3.org/Archives/Public/www-style/2013Sep/0261.html -i18n-ISSUE-292: Synthesised cyrillic italics +i18n-ISSUE-292: Synthesized cyrillic italics Raised By: Internationalization WG (rishida), three weeks after the end of LC Resolution: editorial change, spec updated. Fixed in: https://hg.csswg.org/drafts/rev/3479cdefc59a diff --git a/css-fonts-3/transition-cr-2017.md b/css-fonts-3/transition-cr-2017.md index 372cf2198b7..54d30d55525 100644 --- a/css-fonts-3/transition-cr-2017.md +++ b/css-fonts-3/transition-cr-2017.md @@ -10,7 +10,7 @@ CSS Fonts Module Level 3 https://drafts.csswg.org/css-fonts-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 diff --git a/css-fonts-4/Overview.bs b/css-fonts-4/Overview.bs index 138560f04fa..ac100a74b42 100644 --- a/css-fonts-4/Overview.bs +++ b/css-fonts-4/Overview.bs @@ -4252,7 +4252,7 @@ in all uppercase letters.

    using all-small-caps in acronym-laden text

    Using small capitals to improve readability in acronym-laden text

    -

    Quotes rendered italicised, with small-caps on the first line:

    +

    Quotes rendered italicized, with small-caps on the first line:

    blockquote            { font-style: italic; }
 blockquote:first-line { font-variant: small-caps; }
@@ -5447,7 +5447,7 @@ Feature precedence examples
 
 	If available, a Japanese font "Hiragino Maru Gothic" will be used.  When text
 	rendering occurs, Japanese kana will be proportionally spaced and Latin text will
-	be italicised.  Text rendered with the fallback serif font will use default
+	be italicized.  Text rendered with the fallback serif font will use default
 	rendering properties.
    @@ -6519,7 +6519,7 @@ For someone in Europe who has a Japanese IME in the text input menu, they are. Fingerprinting on Installed Fonts may expose sensitive information in some cases. For example, persecuted minorities risk leaking sensitive information by exposing that they use fonts required for a persecuted minority language; -either by requesting a Web Font from a third pary service, +either by requesting a Web Font from a third party service, or exposing Preinstalled Fonts or User-Installed Fonts associated with that language.

    Does this specification introduce new state for an origin that persists across browsing sessions?

    @@ -6696,7 +6696,7 @@ Changes
  • Remove font-variant @font-face descriptor per WG resolution
  • Remove font-min-size and font-max-size per WG resolution
  • Clarify that font-style 'normal' animates as 'oblique 0deg'
    • -
  • Clarify why specifying incomplete color palettes fror compound fonts is a bad idea
    • +
  • Clarify why specifying incomplete color palettes for compound fonts is a bad idea
  • Add explicit [Exposed=Window] on interfaces
  • Use correct terms, Unicode emoji presentation sequence and Emoji Presentation Participating Code Points
  • Clarify that each string in font-variation-settings is paired with a single number
    • @@ -6708,7 +6708,7 @@ Changes
  • Better define emoji and math generic font families
  • Add font-size: xxx-large
  • Link to CSS Values definition of ex units
    • -
  • Add scientific inferiors axample of font-feature-settings
    • +
  • Add scientific inferiors example of font-feature-settings
  • Clarify that letter-spacing disables optional ligatures
  • Port font-feature-settings property from CSS Fonts 3
  • Port font-variant shorthand property from CSS Fonts 3
    • diff --git a/css-gcpm-3/2009-06-10.html b/css-gcpm-3/2009-06-10.html index 51c5db01796..ea603893014 100644 --- a/css-gcpm-3/2009-06-10.html +++ b/css-gcpm-3/2009-06-10.html @@ -1837,7 +1837,7 @@

    7.1 The of the top border. Inside the 40px border parts, there will be an invisible border part of at least 20px. Inside these invisible border parts, there will be visible border parts, each 20px long with 20px - invisble border parts between them. + invisible border parts between them.
    @@ -1873,7 +1873,7 @@

    7.1 The of the top border. Inside the 40px border parts, there will be an invisible border part of at least 20px. Inside these invisible border parts, there will be visible border parts, each 20px long with 20px - invisble border parts between them. + invisible border parts between them.
    @@ -2727,11 +2727,11 @@

    10.3 The

    Page counters

    Printed publications often show page numbers to indicate the -sequence of papes. Also, it is common to show the total number of +sequence of pages. Also, it is common to show the total number of pages in the document. For example, "page 3 of 5" may be shown at the bottom of a page. -

    This specifiction describes two counters that can be used to +

    This specification describes two counters that can be used to indicate page numbers: ‘page’ and ‘pages’.

    The ‘page’ counter

    @@ -3030,7 +3030,7 @@

    11.1 The

    In the example above, the first double quote (") would be replace by "«", the second would be replaced by "»" etc. In order for this to work, commas would have to be introduced in order to distinguish - between the different sets of replacemenets: + between the different sets of replacements: 

     body { text-replace: "Soviet Union" "Russia", '"' '«' '»' }
@@ -3637,7 +3637,7 @@ 
    15 CMYK colors
    
    Values outside this range are clipped.
 
   
    Unless a color profile is specified, the cmyk() value refers to
-   device-specific colors. A future version of this specifiction will
+   device-specific colors. A future version of this specification will
    describe how to link to color profiles.
 
   
    It is not expected that screen-centric user agents support CMYK colors
@@ -3661,11 +3661,11 @@ 
    16 Creating
    paged presentations
    
 
   
    Printed publications are paged, while screen-based presentations of web
-   pages are most often presented in a continous manner with a scrollbar on
+   pages are most often presented in a continuous manner with a scrollbar on
    the side. There are reasons to believe that screen-based presentations
    also could benefit from using paged presentations. There is nothing in web
    specifications that prevent browsers from adding a page-based mode today.
-   However, most web content is authored and styled with a continous
+   However, most web content is authored and styled with a continuous
    presentation in mind. This could change if it becomes possible to describe
    paged presentations in style sheets.
 
@@ -3948,7 +3948,7 @@ 
    18 Page floats
    
 }
    In the above code, the element is take out of the flow, which is allowed - to contiue on the same page. If the flow should be broken, this code can + to continue on the same page. If the flow should be broken, this code can be used: 
     table.wide { 
diff --git a/css-gcpm-3/2009-06-10.src.html b/css-gcpm-3/2009-06-10.src.html
index 7e63f670da3..e96d78f3d69 100644
--- a/css-gcpm-3/2009-06-10.src.html
+++ b/css-gcpm-3/2009-06-10.src.html
@@ -1426,7 +1426,7 @@ 
    The 'border-parts' properties
    
 border-top-parts: 40px 20px 0 1fr repeat(20px 20px) 0 1fr 40px;
    -

    In this example, there will be a visible 40px border part on each end of the top border. Inside the 40px border parts, there will be an invisible border part of at least 20px. Inside these invisible border parts, there will be visible border parts, each 20px long with 20px invisble border parts between them. +

    In this example, there will be a visible 40px border part on each end of the top border. Inside the 40px border parts, there will be an invisible border part of at least 20px. Inside these invisible border parts, there will be visible border parts, each 20px long with 20px invisible border parts between them.

    @@ -1453,7 +1453,7 @@

    The 'border-parts' properties

    border-top-parts: 40px 20px 0 1fr 20px 20px 0 1fr 40px; -

    In this example, there will be a visible 40px border part on each end of the top border. Inside the 40px border parts, there will be an invisible border part of at least 20px. Inside these invisible border parts, there will be visible border parts, each 20px long with 20px invisble border parts between them. +

    In this example, there will be a visible 40px border part on each end of the top border. Inside the 40px border parts, there will be an invisible border part of at least 20px. Inside these invisible border parts, there will be visible border parts, each 20px long with 20px invisible border parts between them.

    @@ -1990,11 +1990,11 @@

    The ''symbols()'' list-style-type

    Page counters

    Printed publications often show page numbers to indicate the -sequence of papes. Also, it is common to show the total number of +sequence of pages. Also, it is common to show the total number of pages in the document. For example, "page 3 of 5" may be shown at the bottom of a page. -

    This specifiction describes two counters that can be used to +

    This specification describes two counters that can be used to indicate page numbers: ''page'' and ''pages''.

    The ''page'' counter

    @@ -2543,7 +2543,7 @@

    CMYK colors

    Values outside this range are clipped.

    Unless a color profile is specified, the cmyk() value refers to -device-specific colors. A future version of this specifiction will +device-specific colors. A future version of this specification will describe how to link to color profiles.

    It is not expected that screen-centric user agents support CMYK @@ -2565,12 +2565,12 @@

    CMYK colors

    Creating paged presentations

    Printed publications are paged, while screen-based presentations of -web pages are most often presented in a continous manner with a +web pages are most often presented in a continuous manner with a scrollbar on the side. There are reasons to believe that screen-based presentations also could benefit from using paged presentations. There is nothing in web specifications that prevent browsers from adding a page-based mode today. However, most web content is authored and -styled with a continous presentation in mind. This could change if it +styled with a continuous presentation in mind. This could change if it becomes possible to describe paged presentations in style sheets.

    The simplest way to signal that a paged presentation is preferable @@ -2962,7 +2962,7 @@

    Page floats

    In the above code, the element is take out of the flow, which is -allowed to contiue on the same page. If the flow should be broken, +allowed to continue on the same page. If the flow should be broken, this code can be used: 
    diff --git a/css-gcpm-3/uc.html b/css-gcpm-3/uc.html
index 0d34c14f479..61758029205 100644
--- a/css-gcpm-3/uc.html
+++ b/css-gcpm-3/uc.html
@@ -17,9 +17,9 @@ 
    Advanced Multicol Use Cases
    
 
 
      
 
    • a grid-based layout with 8 columns
-
    • a heading that spans all 8 colums
-
    • an image that span the right-most 4 colums, all the way to the page edge
-
    • in introdutcion that spans the left-most 4 column
+
    • a heading that spans all 8 columns
+
    • an image that span the right-most 4 columns, all the way to the page edge
+
    • in introduction that spans the left-most 4 column
 
    
 
 
    We will disregard these components:
@@ -31,7 +31,7 @@ 
    Advanced Multicol Use Cases
    
 
 -->
 
-
+
    ChallegeGrid positioningGCPM alt1GCPM alt2GCPM alt5
    ChallengeGrid positioningGCPM alt1GCPM alt2GCPM alt5
 
 
    #1 Float an image to the right in its containing block.
 
                      
    
@@ -517,7 +517,7 @@ 
    Advanced Multicol Use Cases
    
 
  
 
-
    #22 In a three-column layout, make articles use exactly two balanced columns on the ending page (as The Economist does on occation)
+
    #22 In a three-column layout, make articles use exactly two balanced columns on the ending page (as The Economist does on occasion)
 
 
    (not possible)
 
diff --git a/css-grid-1/issues-cr-2016.bsi b/css-grid-1/issues-cr-2016.bsi
index eec6c4b3618..2b8c0a6fe09 100644
--- a/css-grid-1/issues-cr-2016.bsi
+++ b/css-grid-1/issues-cr-2016.bsi
@@ -70,7 +70,7 @@ Notes:    Fixed in css-inline-3
 Resolved: https://lists.w3.org/Archives/Public/www-style/2017Mar/0060.html
 ----
 Issue 9.
-Summary:  Intrinsic size compuation depends on layout for orthogonal flows
+Summary:  Intrinsic size computation depends on layout for orthogonal flows
 From:     Javier Fernandez
 Comment:  https://github.com/w3c/csswg-drafts/issues/537
 Response: https://github.com/w3c/csswg-drafts/issues/537#issuecomment-268113389
@@ -291,7 +291,7 @@ Closed:   Retracted
 Issue 36.
 Summary:  Placing Against Missing Line Names Needs Example
 From:     Rachel Andrew
-Commment: https://github.com/w3c/csswg-drafts/issues/966
+Comment:  https://github.com/w3c/csswg-drafts/issues/966
 Response: https://github.com/w3c/csswg-drafts/issues/966#issuecomment-277042153
 Response: https://github.com/w3c/csswg-drafts/issues/966#issuecomment-337401055
 Closed:   Rejected
@@ -403,7 +403,7 @@ Closed:   Accepted
 Resolved: Editorial
 ----
 Issue 49.
-Summary:  Error in eample 4
+Summary:  Error in example 4
 From:     Robert DiBlasi
 Comment:  https://github.com/w3c/csswg-drafts/issues/1276
 Response: https://github.com/w3c/csswg-drafts/issues/1276#issuecomment-321384822
@@ -446,7 +446,7 @@ Closed:   Accepted
 Resolved: Editorial
 ----
 Issue 54.
-Summary:  Clarify applicacation of z-index
+Summary:  Clarify application of z-index
 From:     Oriol
 Comment:  https://github.com/w3c/csswg-drafts/issues/1312
 Response: https://github.com/w3c/csswg-drafts/issues/1312#issuecomment-298202507
@@ -541,7 +541,7 @@ Closed:   Accepted
 Resolved: Editorial
 -----
 Issue 65.
-Summary:  Distributing space should clarify maxxing vs summing.
+Summary:  Distributing space should clarify maxing vs summing.
 From:     fantasai
 Comment:  https://github.com/w3c/csswg-drafts/issues/1729
 Closed:   Accepted
diff --git a/css-grid-1/issues-cr-2016.html b/css-grid-1/issues-cr-2016.html
index 82ab7f58c20..90f268be2fc 100644
--- a/css-grid-1/issues-cr-2016.html
+++ b/css-grid-1/issues-cr-2016.html
@@ -110,7 +110,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2016-09-29 CR
    
 Resolved: https://lists.w3.org/Archives/Public/www-style/2017Mar/0060.html ∈
 
     Issue 9. #
-Summary:  Intrinsic size compuation depends on layout for orthogonal flows
+Summary:  Intrinsic size computation depends on layout for orthogonal flows
 From:     Javier Fernandez
 Comment:  https://github.com/w3c/csswg-drafts/issues/537
 Response: https://github.com/w3c/csswg-drafts/issues/537#issuecomment-268113389
@@ -331,7 +331,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2016-09-29 CR
    
 Issue 36. #
 Summary:  Placing Against Missing Line Names Needs Example
 From:     Rachel Andrew
-Commment: https://github.com/w3c/csswg-drafts/issues/966
+Comment:  https://github.com/w3c/csswg-drafts/issues/966
 Response: https://github.com/w3c/csswg-drafts/issues/966#issuecomment-277042153
 Response: https://github.com/w3c/csswg-drafts/issues/966#issuecomment-337401055
 Closed:   Rejected
    
@@ -443,7 +443,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2016-09-29 CR
    
 Resolved: Editorial
 
     Issue 49. #
-Summary:  Error in eample 4
+Summary:  Error in example 4
 From:     Robert DiBlasi
 Comment:  https://github.com/w3c/csswg-drafts/issues/1276
 Response: https://github.com/w3c/csswg-drafts/issues/1276#issuecomment-321384822
@@ -486,7 +486,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2016-09-29 CR
    
 Resolved: Editorial
    
 
     Issue 54. #
-Summary:  Clarify applicacation of z-index
+Summary:  Clarify application of z-index
 From:     Oriol
 Comment:  https://github.com/w3c/csswg-drafts/issues/1312
 Response: https://github.com/w3c/csswg-drafts/issues/1312#issuecomment-298202507
@@ -582,7 +582,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2016-09-29 CR
    
 -
    
 
     Issue 65. #
-Summary:  Distributing space should clarify maxxing vs summing.
+Summary:  Distributing space should clarify maxing vs summing.
 From:     fantasai
 Comment:  https://github.com/w3c/csswg-drafts/issues/1729
 Closed:   Accepted
diff --git a/css-grid-1/issues-cr-2017.bsi b/css-grid-1/issues-cr-2017.bsi
index cdde254ee09..90f8e2c7bc7 100644
--- a/css-grid-1/issues-cr-2017.bsi
+++ b/css-grid-1/issues-cr-2017.bsi
@@ -54,7 +54,7 @@ Summary:  Clarify axis for AMS condition
 From:     Mats Palmgren
 Comment:  https://github.com/w3c/csswg-drafts/issues/2283
 Changes:  https://github.com/w3c/csswg-drafts/commit/4b784426189a2979bf0b396a6ccf8c6b763004a8
-Respone:  https://github.com/w3c/csswg-drafts/issues/2283#issuecomment-363643213
+Response: https://github.com/w3c/csswg-drafts/issues/2283#issuecomment-363643213
 Closed:   Accepted
 Resolved: Editorial
 ----
@@ -318,7 +318,7 @@ Issue 34.
 Summary:  Rename min-size contribution
 From:     Tab Atkins
 Comment:  https://github.com/w3c/csswg-drafts/issues/3277
-Rsponse:  https://github.com/w3c/csswg-drafts/issues/3277#issuecomment-446021037
+Response: https://github.com/w3c/csswg-drafts/issues/3277#issuecomment-446021037
 Changes:  https://github.com/w3c/csswg-drafts/commit/be2c57b3fe5a508008ad4e42d3253463aa851ea6
 Closed:   Accepted
 Resolved: Editorial
@@ -693,7 +693,7 @@ Summary:  Clarify intention of minimum contribution
 From:     fantasai
 Comment:  https://github.com/w3c/csswg-drafts/issues/4016
 Changes:  https://github.com/w3c/csswg-drafts/commit/d5b753c962487bcc446926f7e6107234f8eef56b
-Closed:   Accpeted
+Closed:   Accepted
 Resolved: Editorial
 Verified: reporter is editor
 ----
@@ -820,7 +820,7 @@ Comment:  https://github.com/w3c/csswg-drafts/issues/4783
 Response: https://github.com/w3c/csswg-drafts/issues/4783#issuecomment-587749012
 Closed:   Accepted
 Resolved: CSSWG 2020-07-27
-Veified:  https://github.com/w3c/csswg-drafts/issues/4783#issuecomment-667237434
+Verified: https://github.com/w3c/csswg-drafts/issues/4783#issuecomment-667237434
 ----
 Issue 92.
 Summary:  Definition of fit-content() uses min() and max() backwards
diff --git a/css-grid-1/issues-cr-2017.html b/css-grid-1/issues-cr-2017.html
index 04f50538592..e38eda29f06 100644
--- a/css-grid-1/issues-cr-2017.html
+++ b/css-grid-1/issues-cr-2017.html
@@ -94,7 +94,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2017-12-14 CR
    
 From:     Mats Palmgren
 Comment:  https://github.com/w3c/csswg-drafts/issues/2283
 Changes:  https://github.com/w3c/csswg-drafts/commit/4b784426189a2979bf0b396a6ccf8c6b763004a8
-Respone:  https://github.com/w3c/csswg-drafts/issues/2283#issuecomment-363643213
+Response: https://github.com/w3c/csswg-drafts/issues/2283#issuecomment-363643213
 Closed:   Accepted
 Resolved: Editorial
    
 
    @@ -358,7 +358,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2017-12-14 CR
    
 Summary:  Rename min-size contribution
 From:     Tab Atkins
 Comment:  https://github.com/w3c/csswg-drafts/issues/3277
-Rsponse:  https://github.com/w3c/csswg-drafts/issues/3277#issuecomment-446021037
+Response: https://github.com/w3c/csswg-drafts/issues/3277#issuecomment-446021037
 Changes:  https://github.com/w3c/csswg-drafts/commit/be2c57b3fe5a508008ad4e42d3253463aa851ea6
 Closed:   Accepted
 Resolved: Editorial
    
@@ -733,7 +733,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2017-12-14 CR
    
 From:     fantasai
 Comment:  https://github.com/w3c/csswg-drafts/issues/4016
 Changes:  https://github.com/w3c/csswg-drafts/commit/d5b753c962487bcc446926f7e6107234f8eef56b
-Closed:   Accpeted
+Closed:   Accepted
 Resolved: Editorial
 Verified: reporter is editor
 
    @@ -860,7 +860,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2017-12-14 CR
    
 Response: https://github.com/w3c/csswg-drafts/issues/4783#issuecomment-587749012
 Closed:   Accepted
 Resolved: CSSWG 2020-07-27
-Veified:  https://github.com/w3c/csswg-drafts/issues/4783#issuecomment-667237434
    
+Verified: https://github.com/w3c/csswg-drafts/issues/4783#issuecomment-667237434
 
     Issue 92. #
 Summary:  Definition of fit-content() uses min() and max() backwards
diff --git a/css-grid-1/issues-wd-20150917.bsi b/css-grid-1/issues-wd-20150917.bsi
index fd3ff610067..1ddc2bf5a15 100644
--- a/css-grid-1/issues-wd-20150917.bsi
+++ b/css-grid-1/issues-wd-20150917.bsi
@@ -314,7 +314,7 @@ Closed:   Accepted
 Resolved: Bugfix
 ----
 Issue 37.
-Summary:  Define "last baseline" for grid contianer
+Summary:  Define "last baseline" for grid container
 From:     Mats Palmgren
 Comment:  https://lists.w3.org/Archives/Public/www-style/2016Mar/0079.html
 Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0372.html
diff --git a/css-grid-1/issues-wd-20150917.html b/css-grid-1/issues-wd-20150917.html
index 9baa1d1a3e7..4ee5335d9df 100644
--- a/css-grid-1/issues-wd-20150917.html
+++ b/css-grid-1/issues-wd-20150917.html
@@ -347,7 +347,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2015-09-17 WD
    
 Resolved: Bugfix
    
 
     Issue 37. #
-Summary:  Define "last baseline" for grid contianer
+Summary:  Define "last baseline" for grid container
 From:     Mats Palmgren
 Comment:  https://lists.w3.org/Archives/Public/www-style/2016Mar/0079.html
 Response: https://lists.w3.org/Archives/Public/www-style/2016Apr/0372.html
diff --git a/css-grid-1/issues-wd-20160519.bsi b/css-grid-1/issues-wd-20160519.bsi
index 471a8f2b5b6..3754b8bec8f 100644
--- a/css-grid-1/issues-wd-20160519.bsi
+++ b/css-grid-1/issues-wd-20160519.bsi
@@ -220,7 +220,7 @@ From:      Mats Palmgren
 Comment:   https://github.com/w3c/csswg-drafts/issues/472
 Response:  https://github.com/w3c/csswg-drafts/issues/472#issuecomment-248655700
 Changes:   https://hg.csswg.org/drafts/rev/d55bbbd4cee5
-Closed:    Indeterminite (made undefined)
+Closed:    Indeterminate (made undefined)
 Resolved:  TPAC 2016
 ----
 Issue 27.
diff --git a/css-grid-1/issues-wd-20160519.html b/css-grid-1/issues-wd-20160519.html
index 8520b159608..c8799d2cca1 100644
--- a/css-grid-1/issues-wd-20160519.html
+++ b/css-grid-1/issues-wd-20160519.html
@@ -260,7 +260,7 @@ 
    CSS Grid Layout Level 1 Disposition of Comments for 2016-05-19 WD
    
 Comment:   https://github.com/w3c/csswg-drafts/issues/472
 Response:  https://github.com/w3c/csswg-drafts/issues/472#issuecomment-248655700
 Changes:   https://hg.csswg.org/drafts/rev/d55bbbd4cee5
-Closed:    Indeterminite (made undefined)
+Closed:    Indeterminate (made undefined)
 Resolved:  TPAC 2016
    
 
     Issue 27. #
diff --git a/css-grid-3/Overview.bs b/css-grid-3/Overview.bs
index 27e95979c0c..8d9746692a3 100644
--- a/css-grid-3/Overview.bs
+++ b/css-grid-3/Overview.bs
@@ -137,7 +137,7 @@ repeat(auto-fit)
 
    
 Masonry Layout Algorithm
    
 
-Items are placed in order-modifed document order, but items with a definite placement are placed before items with an indefinite position (as in regular grid layout). For each of the tracks in the [=grid axis=], keep a running position initialized to zero. For each item placed at the first implicit line in the [=masonry axis=] in Grid Item Placement step 1 above:
+Items are placed in order-modified document order, but items with a definite placement are placed before items with an indefinite position (as in regular grid layout). For each of the tracks in the [=grid axis=], keep a running position initialized to zero. For each item placed at the first implicit line in the [=masonry axis=] in Grid Item Placement step 1 above:
 
      
 	
    1. Position the item at the content edge of the grid container in the [=masonry axis=] and at its start track in the [=grid axis=].
      2. 
 	
    2. Calculate the size of the containing block and then layout the item.  Then, calculate its resulting margin-box in the [=masonry axis=]. Set the [=running position=] of the [=grid axis=] tracks the item spans to the maximum of margin-box-end + grid-gap and the current [=running position=] of those tracks.
      3. 
@@ -177,7 +177,7 @@ The [[#masonry-layout-algorithm]] above can be modified in two ways, using the n
 
    
 
 
-First, picking definite items first for placement can be inhibited by specifying the ''masonry-auto-flow/ordered'' keyword so that a plain order-modifed document order is used instead.  Second, instead of placing the items in the track(s) with the most remaining space as described above we can place them one after another in the [=grid axis=] by specifying the ''masonry-auto-flow/next'' keyword, for example:
+First, picking definite items first for placement can be inhibited by specifying the ''masonry-auto-flow/ordered'' keyword so that a plain order-modified document order is used instead.  Second, instead of placing the items in the track(s) with the most remaining space as described above we can place them one after another in the [=grid axis=] by specifying the ''masonry-auto-flow/next'' keyword, for example:
 
 
    
 ```css
diff --git a/css-highlight-api-1/Overview.bs b/css-highlight-api-1/Overview.bs
index 6b1c794f9c0..1dc91d115a1 100644
--- a/css-highlight-api-1/Overview.bs
+++ b/css-highlight-api-1/Overview.bs
@@ -474,7 +474,7 @@ Range Updating and Invalidation
 		are strongly encouraged to user {{StaticRange}}s
 		in order to avoid this costly but unnecessary step.
 
-		Conversedly, authors who use {{StaticRange}}s
+		Conversely, authors who use {{StaticRange}}s
 		should observe and react to DOM changes,
 		by discarding stale [=ranges=] or [=custom highlights=]
 		and recreating new ones.
diff --git a/css-images-3/issues-cr-2012.html b/css-images-3/issues-cr-2012.html
index 7bada923e16..3ffd8dc78a0 100644
--- a/css-images-3/issues-cr-2012.html
+++ b/css-images-3/issues-cr-2012.html
@@ -157,7 +157,7 @@ 
    CSS Image Values and Replaced Content Level 3 Disposition of Comments for 20
 Open
 
     Issue 16. #
-Summary:  Limit interopolation of repeating gradients to same number of color stops
+Summary:  Limit interpolation of repeating gradients to same number of color stops
 From:     Dirk Schulze
 Comment:  https://lists.w3.org/Archives/Public/www-style/2013Aug/0294.html (thread)
 Open
    
diff --git a/css-images-3/issues-cr-2012.json b/css-images-3/issues-cr-2012.json
index f96a72d01df..062947229ea 100644
--- a/css-images-3/issues-cr-2012.json
+++ b/css-images-3/issues-cr-2012.json
@@ -236,7 +236,7 @@
 		},
 		{
 			"id": "16",
-			"summary": "Limit interopolation of repeating gradients to same number of color stops",
+			"summary": "Limit interpolation of repeating gradients to same number of color stops",
 			"status": "accepted",
 			"from": "Dirk Schulze",
 			"comment": [
diff --git a/css-images-3/issues-cr-2012.txt b/css-images-3/issues-cr-2012.txt
index 56408e15b15..3c5bb067de5 100644
--- a/css-images-3/issues-cr-2012.txt
+++ b/css-images-3/issues-cr-2012.txt
@@ -152,7 +152,7 @@ Comment:  https://lists.w3.org/Archives/Public/www-style/2013Aug/0300.html
 Open
 ----
 Issue 16.
-Summary:  Limit interopolation of repeating gradients to same number of color stops
+Summary:  Limit interpolation of repeating gradients to same number of color stops
 From:     Dirk Schulze
 Comment:  https://lists.w3.org/Archives/Public/www-style/2013Aug/0294.html
 Open
diff --git a/css-images-3/issues-cr-2012.yaml b/css-images-3/issues-cr-2012.yaml
index af4ea8e756b..07b53c75c27 100644
--- a/css-images-3/issues-cr-2012.yaml
+++ b/css-images-3/issues-cr-2012.yaml
@@ -209,7 +209,7 @@ issue:
     tag: []
     filtered: []
   - id: 16
-    summary: Limit interopolation of repeating gradients to same number of color stops
+    summary: Limit interpolation of repeating gradients to same number of color stops
     status: accepted
     from: Dirk Schulze
     comment:
diff --git a/css-images-4/Overview.bs b/css-images-4/Overview.bs
index 690827d7a50..59c2a2f1c80 100644
--- a/css-images-4/Overview.bs
+++ b/css-images-4/Overview.bs
@@ -1975,7 +1975,7 @@ Overriding Image Resolutions: the 'image-resolution' property {#the-image-resolu
 
 	
    
 		Printers tend to have substantially higher resolution than computer monitors;
-		due to this, an image that looks fine on the screen may look pixellated when printed out.
+		due to this, an image that looks fine on the screen may look pixelated when printed out.
 		The 'image-resolution' property can be used to embed a high-resolution image into the document
 		and maintain an appropriate size,
 		ensuring attractive display both on screen and on paper:
diff --git a/css-inline-3/Overview.bs b/css-inline-3/Overview.bs
index 33f69025f0c..664e2a9bdcf 100644
--- a/css-inline-3/Overview.bs
+++ b/css-inline-3/Overview.bs
@@ -2678,7 +2678,7 @@ Interaction with floats
    
 	however it’s yet unclear how the underlying layout model
 	would distinguish between the two cases.
 
-
    
+
    
 Interaction with Fragmentation (Pagination)
    
 
 	Since a single glyph cannot be fragmented across
@@ -3009,7 +3009,7 @@ Changes
 			(Issue 719)
 
 		
  • 
-			Miscellaneous small fixes, clarifications, and editoial improvements.
+			Miscellaneous small fixes, clarifications, and editorial improvements.
 	
 
 	Changes since the
diff --git a/css-logical-1/Overview.bs b/css-logical-1/Overview.bs
index 5a23a8693cb..c1283e31cfe 100644
--- a/css-logical-1/Overview.bs
+++ b/css-logical-1/Overview.bs
@@ -493,7 +493,7 @@ Flow-relative Offsets:
 the 'inset-block-start', 'inset-block-end', 'inset-inline-start', 'inset-inline-end' properties and 'inset-block', 'inset-inline', and 'inset' shorthands
 
   The 'top', 'left', 'bottom', 'right' physical properties,
-  their 'inset-block-start', 'inset-block-end', 'inset-inline-start', 'inset-inline-end' flow-relative correspondants,
+  their 'inset-block-start', 'inset-block-end', 'inset-inline-start', 'inset-inline-end' flow-relative correspondents,
   and the 'inset-block', 'inset-inline', and 'inset' shorthands,
   are collectively known as the inset properties.
 
diff --git a/css-multicol-1/issues-2011.html b/css-multicol-1/issues-2011.html
index 2514fc846ee..816b76dd3c1 100644
--- a/css-multicol-1/issues-2011.html
+++ b/css-multicol-1/issues-2011.html
@@ -372,7 +372,7 @@ 
    CSS Multi-column Layout Module Level 1 Disposition of Comments for 2011-04-1
 
     Issue 38. #
 From:     Sam Sneddon
-Summary:  Psuedo-algorithm doesn't say when
+Summary:  Pseudo-algorithm doesn't say when
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488#issuecomment-377432504
 Open
    
diff --git a/css-multicol-1/issues-2011.txt b/css-multicol-1/issues-2011.txt
index 04ec00f528d..1b8a9f55df7 100644
--- a/css-multicol-1/issues-2011.txt
+++ b/css-multicol-1/issues-2011.txt
@@ -332,7 +332,7 @@ Resolved: https://github.com/w3c/csswg-drafts/issues/2309#issuecomment-380733360
 ----
 Issue 38.
 From:     Sam Sneddon
-Summary:  Psuedo-algorithm doesn't say when
+Summary:  Pseudo-algorithm doesn't say when
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488#issuecomment-377432504
 Closed:   Editorial
diff --git a/css-multicol-1/issues-dec-2020.txt b/css-multicol-1/issues-dec-2020.txt
index f006e3196c2..a04752f9db4 100644
--- a/css-multicol-1/issues-dec-2020.txt
+++ b/css-multicol-1/issues-dec-2020.txt
@@ -332,7 +332,7 @@ Resolved: https://github.com/w3c/csswg-drafts/issues/2309#issuecomment-380733360
 ----
 Issue 38.
 From:     Sam Sneddon
-Summary:  Psuedo-algorithm doesn't say when
+Summary:  Pseudo-algorithm doesn't say when
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488#issuecomment-377432504
 Closed:   Accepted
diff --git a/css-multicol-1/issues.html b/css-multicol-1/issues.html
index 4ff94086d08..7e6a7d5c244 100644
--- a/css-multicol-1/issues.html
+++ b/css-multicol-1/issues.html
@@ -362,7 +362,7 @@ 
    CSS Multi-column Layout Module Level 1 Disposition of Comments for 2021-02-1
 
     Issue 38. #
 From:     Sam Sneddon
-Summary:  Psuedo-algorithm doesn't say when
+Summary:  Pseudo-algorithm doesn't say when
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488
 Comment:  https://github.com/w3c/csswg-drafts/issues/2488#issuecomment-377432504
 Closed:   Accepted
diff --git a/css-multicol-1/last-call.html b/css-multicol-1/last-call.html
index 157cfac0e69..cc39eaf376e 100644
--- a/css-multicol-1/last-call.html
+++ b/css-multicol-1/last-call.html
@@ -203,7 +203,7 @@ 
    CSS3 Multi-column Layout Module – disposition of comments
    
 
    • About overflow inside and outside the multicolum element:
 
 what happens if Example XVIII has an element that floats on
-the rigth? Is the element clipped (showing only the right part), does
+the right? Is the element clipped (showing only the right part), does
 the element intrude (ignoring the side of the float), does overflow
 apply?
 
diff --git a/css-namespaces-3/issues-1.txt b/css-namespaces-3/issues-1.txt
index 69495d134f1..feb6bf13504 100644
--- a/css-namespaces-3/issues-1.txt
+++ b/css-namespaces-3/issues-1.txt
@@ -103,7 +103,7 @@ Issue 11.
 Summary:  Use RFC2119 for all requirements
 From:     Karl Dubost for QA Review
 Key:      [css3-namespace] Requirements of the document as framed by RFC 2119
-Comment:  htttp://lists.w3.org/Archives/Public/www-style/2006Sep/0022.html
+Comment:  http://lists.w3.org/Archives/Public/www-style/2006Sep/0022.html
 Response: http://lists.w3.org/Archives/Public/www-style/2006Sep/0190.html
 Closed:   Rejected
 Verified: http://lists.w3.org/Archives/Public/www-style/2006Sep/0264.html
diff --git a/css-overflow-3/Overview.bs b/css-overflow-3/Overview.bs
index d065dc639f5..dc74d2deaa6 100644
--- a/css-overflow-3/Overview.bs
+++ b/css-overflow-3/Overview.bs
@@ -25,8 +25,8 @@ Ignored Vars: B, P
 Ignored Terms: padding edge, viewport, line box, flex order, -webkit-box-orient
 At Risk: the 'max-lines' property
 Status Text:
-   The desciption of 'overflow' and its longhands is considered
-   significantly more complete and correct than previous working drafs
+   The description of 'overflow' and its longhands is considered
+   significantly more complete and correct than previous working drafts
    or than [[CSS2]],
    but a few questions and issues remain open.
    ''overflow: clip' and 'overflow-clip-margin' are rather new,
@@ -97,7 +97,7 @@ Introduction
 	Note: This specification also reproduces the definition of the 'text-overflow' property
 	previously defined in [[CSS-UI-3]],
 	with no addition or modification,
-	in order to present 'text-overflow' and 'block-ellipsis' toghether.
+	in order to present 'text-overflow' and 'block-ellipsis' together.
 
 
    
 Value Definitions
    
@@ -391,7 +391,7 @@ Scrolling and Clipping Overflow: the 'overflow-x', 'overflow-y', and 'overflow'
 			nor allow scrolling by direct intervention of the user,
 			such as dragging on a touch screen
 			or using the scrolling wheel on a mouse.
-			However, the content must still be scrollable programatically,
+			However, the content must still be scrollable programmatically,
 			for example using the mechanisms defined in [[CSSOM-VIEW]],
 			and the box is therefore still a scroll container.
 
@@ -544,7 +544,7 @@ Expanding Clipping Bounds: the 'overflow-clip-margin' property
 	of the same cumulative offset from the box’s [=border edge=].
 	See [[css-backgrounds-3#corner-shaping]].
 
-	ISSUE(5896): Should this be appying the 1 + (r-1)3 adjustment
+	ISSUE(5896): Should this be applying the 1 + (r-1)3 adjustment
 	to the absolute offset or just to <> edge (applying the offset absolutely)?
 
 	Note: This property has no effect on boxes
@@ -1008,7 +1008,7 @@ Limiting Visible Lines: the 'line-clamp' shorthand property
 	for the 'max-lines', 'block-ellipsis', and 'continue' properties.
 
 	Issue: For the time being,
-	experiemental implementations are encouraged
+	experimental implementations are encouraged
 	to follow the full behavior defined by this shorthand and its longhands,
 	but to only expose the shorthand to authors.
 	This is in order to facilitate further tweaking,
@@ -1062,7 +1062,7 @@ Limiting Visible Lines: the 'line-clamp' shorthand property
 				Cheese is Actually Made of Milk!
 				Investigative reporters at the World Wide Web Press Corps
 				have discovered the secret of cheese.
-				Tracing through byzantine layers of bureacracy and shadow corporations,
+				Tracing through byzantine layers of bureaucracy and shadow corporations,
 				our crack team of journalists have traced the source of camembert.
 			
 		
@@ -1265,7 +1265,7 @@ Once it is sufficiently stable in this specification,
 			* [=Positioned=] elements whose static position is in the discarded content are not rendered.
 
 				Issue(2971): Are we sure about that?
-				Discussions in the Syndey F2F meeting
+				Discussions in the Sydney F2F meeting
 				seemed to generally converge on this,
 				but other possibilities were raised.
 
@@ -1286,7 +1286,7 @@ Once it is sufficiently stable in this specification,
 			The effect on [=multi-column containers=] is to discard any [=overflow column=].
 
 			Note: In the case of parallel fragmentation flows,
-			content occuring after the fragmentation break in the box tree
+			content occurring after the fragmentation break in the box tree
 			could still be rendered,
 			if it is laid out above the position
 			representing the end of this fragmentation container.
@@ -1336,7 +1336,7 @@ Once it is sufficiently stable in this specification,
 	
 
 
-
    Appendex A. Privacy and Security Considerations
    
+
    Appendix A. Privacy and Security Considerations
    
 ===============================================
 
 This specification introduces no new privacy or security concerns.
diff --git a/css-overflow-4/Overview.bs b/css-overflow-4/Overview.bs
index 9f57d5a704d..9329e9ec199 100644
--- a/css-overflow-4/Overview.bs
+++ b/css-overflow-4/Overview.bs
@@ -419,14 +419,14 @@ that has 'overflow'
 other than ''overflow/visible''.
 
 Even though this property is not inherited,
-annonymous block container boxes generated to
+anonymous block container boxes generated to
 establish the line box's inline formatting context (see [=block container=])
 are ignored,
 and the value of the property that applies is the one
-on the non annomymous box.
+on the non anonymous box.
 This can be seen in the “nested paragraph” part of example 7:
-even though the word “NESTED” is wrapped in an annoymous block container
-whose 'text-overflow' property has the intial value,
+even though the word “NESTED” is wrapped in an anonymous block container
+whose 'text-overflow' property has the initial value,
 it is ellipsed.
 
 Text can overflow for example when it is prevented from wrapping
diff --git a/css-overscroll-1/README.md b/css-overscroll-1/README.md
index b6d44ebb495..bb85e5c0ec1 100644
--- a/css-overscroll-1/README.md
+++ b/css-overscroll-1/README.md
@@ -34,4 +34,4 @@ where:
 * contain - Hint to disable scroll chaining. The user agent may show an appropriate overscroll affordance. If the scroll chaining would trigger a non-scroll action, such as a navigation action, this property should be a hint to disable the navigation action.
 * none - Same as contain but also hint that no overscroll affordance should be triggered.
 
-This should apply to all, non-programatic, user scroll actions.
+This should apply to all, non-programmatic, user scroll actions.
diff --git a/css-page-3/Overview.bs b/css-page-3/Overview.bs
index 2312387fa0e..31f2bd2624d 100644
--- a/css-page-3/Overview.bs
+++ b/css-page-3/Overview.bs
@@ -421,7 +421,7 @@ box:
 	If the UA supports the 'direction' and 'writing-mode' properties
 	from the CSS 3 Writing Modes Module [[CSS-WRITING-MODES-3]], it must
 	determine
-	the page progression is determed by the principal writing mode.
+	the page progression is determined by the principal writing mode.
 
 	In documents with a left-to-right page progression
 	the first page of the document is a right page, and vice versa.
@@ -2193,7 +2193,7 @@ Using named pages: 'page'
 		In Japanese documents, sometimes different parts of a single document
 		will have different kihon hanmen. [[JLREQ]]
 		The 'page' property, together with ''@page'' rules specifying different page widths,
-		can accomodate this type of layout:
+		can accommodate this type of layout:
 		
     		<!DOCTYPE html>
 		<html lang="ja">
diff --git a/css-page-template-1/Overview.html b/css-page-template-1/Overview.html
index a4f71be0f5d..2a593c4a84c 100644
--- a/css-page-template-1/Overview.html
+++ b/css-page-template-1/Overview.html
@@ -837,7 +837,7 @@ 
    Issue manager
    
             
         
         -->
-  
+  
   
-        
+        
         
 
@@ -732,7 +732,7 @@ Box Edges for Sizing: the 'box-sizing' property
 
 	
    To avoid ambiguities,
 	specification authors should avoid ambiguous uses of terms such as width or height without further qualification,
-	and should explicitely refer and link to
+	and should explicitly refer and link to
 	the inner size,
 	the outer size,
 	the size of the border-box,
diff --git a/css-sizing-4/Overview.bs b/css-sizing-4/Overview.bs
index 00d73898849..391a6eb0d0a 100644
--- a/css-sizing-4/Overview.bs
+++ b/css-sizing-4/Overview.bs
@@ -31,7 +31,7 @@ spec:css-align-3; type:value; text:stretch
 
 
@@ -429,7 +429,7 @@ Min/Max Size Transfers
 	Note: The basic principle is that sizing constraints
 	transfer through the aspect-ratio to the other side
 	to preserve the aspect ratio to the extent that they can
-	without violating any sizes specified explictly on that affected axis.
+	without violating any sizes specified explicitly on that affected axis.
 	
 
 	
    
@@ -948,7 +948,7 @@ Recent Changes
 			Note: The basic principle is that sizing constraints
 			transfer through the aspect-ratio to the other side
 			to preserve the aspect ratio to the extent that they can
-			without violating any sizes specified explictly on that affected axis.
+			without violating any sizes specified explicitly on that affected axis.
 			
 		
 
diff --git a/css-speech-1/Overview.bs b/css-speech-1/Overview.bs
index 6c525ebbb65..50bd0668e07 100644
--- a/css-speech-1/Overview.bs
+++ b/css-speech-1/Overview.bs
@@ -206,7 +206,7 @@ The 'voice-volume' property
 	
    
 
 	The 'voice-volume' property allows authors to control
-	the amplitude of the audio waveform generated by the speech synthesiser,
+	the amplitude of the audio waveform generated by the speech synthesizer,
 	and is also used to adjust the relative volume level of audio cues
 	within the [=aural box model=] of the selected element.
 
@@ -1222,7 +1222,7 @@ The 'voice-pitch' property
 	For example, CSS Speech pitch keywords and relative changes (frequency, semitone or percentage)
 	are not mutually-exclusive, due to how values are inherited and combined for selected elements.
 
-	
    
+	
    
 		
    <>
 		
    
 			A value in frequency units (Hertz or kiloHertz, e.g. ''100Hz'', ''+2kHz'').
diff --git a/css-syntax-3/Overview.bs b/css-syntax-3/Overview.bs
index 2eda4ab54fe..49523f13efa 100644
--- a/css-syntax-3/Overview.bs
+++ b/css-syntax-3/Overview.bs
@@ -3740,7 +3740,7 @@ Changes from CSS 2.1 and Selectors Level 3
 
 		
  • 
 			Refer to [[!ENCODING]]
-			rather than the IANA registery for character encodings.
+			rather than the IANA registry for character encodings.
 
 	
 
@@ -3829,7 +3829,7 @@ Changes from CSS 2.1 and Selectors Level 3
 			and lets the next declaration begin.
 
 		
  • 
-			The handling of some miscellanous "special" tokens
+			The handling of some miscellaneous "special" tokens
 			(like an unmatched <}-token>)
 			showing up in various places in the grammar
 			has been specified with some reasonable behavior shown by at least one browser.
diff --git a/css-tables-3/Overview.bs b/css-tables-3/Overview.bs
index 77481919582..71b3f768a70 100644
--- a/css-tables-3/Overview.bs
+++ b/css-tables-3/Overview.bs
@@ -137,7 +137,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 		
  • Its table-root containing:
 		
      
 			
    • Zero, one or more table rows, optionally in row groups,
-				
+				
 			
    • Optionally: one or more table columns,
 				optionally in column groups
 			
    • Optionally: one or more table caption.
@@ -309,8 +309,8 @@ spec:css-sizing-3; type:property; text:box-sizing
 				Table-cells which cover more than one slot do so densely, 
 					meaning the set of slots they cover can always be described as a set of four strictly-positive integers (rowStart, colStart, rowSpan, colSpan)
 					such that a slot (r,c) is covered by the table-cell 
-						if and only if r lies in the interval between rowStart (included) and rowStart+rowSpan (exculded), 
-						and c lies in the interval between colStart (included) and colStart+colSpan (exculded);
+						if and only if r lies in the interval between rowStart (included) and rowStart+rowSpan (excluded), 
+						and c lies in the interval between colStart (included) and colStart+colSpan (excluded);
 				
 				Such table-cell is said to originate from row rowStart and column colStart.
 				Also:
@@ -466,7 +466,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 					their computed padding is “0px”,
 					their computed border-style is “none”.
 					
-				It is also woth reminding that an anonymous box inherits property values through the box tree.
+				It is also worth reminding that an anonymous box inherits property values through the box tree.
 
 			
 
@@ -653,7 +653,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 		Apply the HTML5 Table Formatting algorithm,
 			where boxes act like the HTML element equivalent to their display type,
 			and use the attributes of their originating element if and only if it is an HTML element of the same type
-			(otherwise, they act like if they didnt't have any attribute).
+			(otherwise, they act like if they didn't have any attribute).
 
 		
      
 			
@@ -820,7 +820,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 			(see [[#border-collapsing]]).
 
 			A <a>table-root</a> is said to be laid out <dfn>in collapsed-borders mode</dfn> in this case.
-			Otherwhise, the <a>table-root</a> is said to be laid out <dfn>in separated-borders mode</dfn>.
+			Otherwise, the <a>table-root</a> is said to be laid out <dfn>in separated-borders mode</dfn>.
 
 			<!--——————————————————————————————————————————————————————————————————————————-->
 			<h5 id="border-spacing-property">The Border-Spacing property</h5>
@@ -1062,7 +1062,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 
 		<ul>
 			<li>Harmonize the <a>table-root</a> border-{top,bottom,left,right}
-					with the corresponding border of all cells forming the border of the table (indenpendently),
+					with the corresponding border of all cells forming the border of the table (independently),
 					without actually modifying the border properties of the <a>table-root</a>.<br>
 				<br>
 				If the table and the cell border styles have the same specificity,
@@ -1247,7 +1247,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 							<div class="note">
 								When the table is laid out <a>in collapsed-borders mode</a>, 
 								the border value to deduce is half the value of the winning border value on each side
-								(see <a href="#border-conflict-resolution-algorithm">conflict resolution explaination note</a>)
+								(see <a href="#border-conflict-resolution-algorithm">conflict resolution explanation note</a>)
 							</div>
 					</ul>
 					
@@ -1639,7 +1639,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 			<p id="width-distribution-principles-r3">
 				<b>Rule 3: </b>
 				<span>
-					The sum of width assgined to all columns should be equal to the <a>assignable table width</a>.
+					The sum of width assigned to all columns should be equal to the <a>assignable table width</a>.
 				</span>
 
 			<style>
@@ -2202,7 +2202,7 @@ spec:css-sizing-3; type:property; text:box-sizing
 					</style>
 
 					<p id="min-content-and-percentages">
-						Intersting test cases about min-content and content using percentage sizes:
+						Interesting test cases about min-content and content using percentage sizes:
 						<ul class="compact">
 							<li><a href="https://jsfiddle.net/gzapbyeg/1/">Case 10</a>.
 							<li><a href="https://jsfiddle.net/gzapbyeg/2/">Case 11</a>.
@@ -2529,7 +2529,7 @@ With a table-root as containing block</h3>
 
 		<figure style="margin: 0">
 			<figcaption style="text-align: left; font-style: normal;">
-				The figure below shows how a box absolutely-positioned relative to a table should be rendred. <br/><br>
+				The figure below shows how a box absolutely-positioned relative to a table should be rendered. <br/><br>
 				The <b>yellow</b> area is the table content edge, yellow arrows the table margins. <br/>
 				The <b>green</b> area is the table caption, green arrows the caption margins. <br/>
 				The <b>blue</b> area is the table background area, and the darker blue area where the table border area. <br/>
@@ -2673,7 +2673,7 @@ With a table-internal box as non-containing block parent</h3>
 			<ul>
 				<li>Backgrounds, borders and outlines painted relative to the content-box of a table-root are painted relative to the rectangular area occupied by the table grid and its border spacings.
 				<li>Backgrounds, borders and outlines painted relative to the padding-box of a table-root are painted relative to the rectangular area occupied by the table grid and its border spacings, extended on each side by the table-root padding.
-				<li>Backgrounds, borders and outlines painted relative to the border-box of a table-root are painted relative to the rectangular area occuped by the table grid and its border spacings, extended on each side by the table-root padding and border-width.
+				<li>Backgrounds, borders and outlines painted relative to the border-box of a table-root are painted relative to the rectangular area occupied by the table grid and its border spacings, extended on each side by the table-root padding and border-width.
 			</ul>
 
 			<div class="note">
@@ -2691,7 +2691,7 @@ With a table-internal box as non-containing block parent</h3>
 
 			<p class="note">
 				The rules for background and borders painting defined in [[#drawing-backgrounds-and-borders]]
-					still apply if they are not overriden.
+					still apply if they are not overridden.
 
 			Borders of a non-<a href="#empty-table">empty</a> <a>table-root</a> are not painted <a>in collapsed-borders mode</a>,
 				except if the 'border-image' property is set.
@@ -2988,7 +2988,7 @@ Using CSS Tables does not incur any privacy risk to mitigate.
 			</a>
 		</summary><aside>
 			Also <a href="https://jsfiddle.net/6L94pxgn/3/">@lt;fieldset></a>.
-			This specification says that Chrome and Firefox are worng.<br/>
+			This specification says that Chrome and Firefox are wrong.<br/>
 			[[#style-overrides]]
 		</aside></details>
 	</li>
@@ -3187,7 +3187,7 @@ Using CSS Tables does not incur any privacy risk to mitigate.
 		The default style sheet for HTML4 illustrates how its model maps to css properties and values:
 
 		<div class="note">
-			Some extensions to CSS have been used for contraints not mappable to current CSS constructs
+			Some extensions to CSS have been used for constraints not mappable to current CSS constructs
 			</div>
 
 		<pre class="lang-css">
diff --git a/css-template-1/Overview.html b/css-template-1/Overview.html
index 6ee369b3962..a5cd3ed4888 100644
--- a/css-template-1/Overview.html
+++ b/css-template-1/Overview.html
@@ -2081,7 +2081,7 @@ <h3 id=slot-sizes><span class=secno>3.7. </span>Calculating the size of the
       <a href="#ltlengthgt"><var>&lt;length&gt;</var></a> values, ‘<code
       class=css>*</code>’, <var>&lt;fraction&gt;</var> values, or any
       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.,
+      the sum of the slot's left and right margin, border and padding (i.e.,
       any ‘<a href="#margin-left"><code
       class=property>margin-left</code></a>’, ‘<a
       href="#margin-right"><code class=property>margin-right</code></a>’,
@@ -3036,7 +3036,7 @@ <h2 id=absolute><span class=secno>5. </span>Comparison with ‘<code
    rel=biblioentry>[CSS-GRID-1]<!--{{!CSS-GRID-1}}--></a>), which is an
    element that uses the ‘<a href="#grid"><code
    class=property>grid</code></a>’ properties to define a grid, just like a
-   <a href="#grid-element."><em>grid element,</em></a> but its chidren ignore
+   <a href="#grid-element."><em>grid element,</em></a> but its children ignore
    the ‘<a href="#flow0"><code class=property>flow</code></a>’ property
    and are instead automatically made into separate flows and positioned in
    subsequent slots of the grid. (Although there are also properties to set
@@ -3214,7 +3214,7 @@ <h3 id=the-blank-pseudo-element><span class=secno>6.2. </span>The ‘<code
    looks empty is not necessarily “blank,” although that is usually the
    case, given the initial value of 'content'.) </code>
 
-  <div class=exmaple>
+  <div class=example>
    <p>For example, slots a, b and c in the following document are blank, but
     slot * is not, even though slots b and c do not look empty, (because they
     have generated content) and slot d does look empty (because its 'content'
@@ -4311,7 +4311,7 @@ <h2 id=chains><span class=secno>10. </span>Chaining slots: the ‘<a
 </pre>
   </div>
 
-  <p class=note>Note: For more anaylysis of the possibilities and limits of
+  <p class=note>Note: For more analysis of the possibilities and limits of
    non-rectangular slots, see the PhD thesis of César Acebal <a
    href="#ref-ACEBAL2010"
    rel=biblioentry>[ACEBAL2010]<!--{{ACEBAL2010}}--></a>.
diff --git a/css-template-1/Overview.src.html b/css-template-1/Overview.src.html
index cea8981fc16..880a234720b 100644
--- a/css-template-1/Overview.src.html
+++ b/css-template-1/Overview.src.html
@@ -1298,7 +1298,7 @@ <h3 id=grid-shorthand >The 'grid' and 'grid-template' shorthand
 </ul>
 
 <p>The 'grid' property is a shorthand for setting
-'grid-template-areas', 'grid-template-rows', 'grid-template'columns',
+'grid-template-areas', 'grid-template-rows', 'grid-template-columns',
 'grid-auto-rows', 'grid-auto-columns', and 'grid-auto-flow' in a
 single declaration. See [[CSS3-GRID-LAYOUT]].
 
@@ -1442,7 +1442,7 @@ <h3 id=slot-sizes>Calculating the size of the grid</h3>
 only <var>&lt;length&gt;</var> values, '*',
 <var>&lt;fraction&gt;</var> values, or any combination of those), then
 <var>MINW</var> is the sum of the slot's left and right margin,
-border and paddding (i.e., any 'margin-left', 'margin-right',
+border and padding (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
 counted as 0 for this purpose. <span class=note>(Note that
@@ -2279,7 +2279,7 @@ <h2 id=absolute>Comparison with 'display: grid' and 'display:
 make an element into a <em>grid container,</em> (see
 [[!CSS3-GRID-LAYOUT]]), which is an element that uses the 'grid'
 properties to define a grid, just like a <em>grid element,</em> but
-its chidren ignore the 'flow' property and are instead automatically
+its children ignore the 'flow' property and are instead automatically
 made into separate flows and positioned in subsequent slots of the
 grid. (Although there are also properties to set their positions
 explicitly.)
@@ -2423,7 +2423,7 @@ <h3>The ''::blank()'' pseudo-element</h3>
 “blank,” although that is usually the case, given the initial value of
 'content'.)
 
-<div class=exmaple>
+<div class=example>
 <p>For example, slots a, b and c in the following document are blank,
 but slot * is not, even though slots b and c do not look empty,
 (because they have generated content) and slot d does look empty
@@ -3378,7 +3378,7 @@ <h2 id=chains>Chaining slots: the 'chains' property</h2>
 </pre>
 </div>
 
-<p class=note>Note: For more anaylysis of the possibilities and limits
+<p class=note>Note: For more analysis of the possibilities and limits
 of non-rectangular slots, see the PhD thesis of César Acebal
 [[ACEBAL2010]].
 
diff --git a/css-template-1/new2.html b/css-template-1/new2.html
index bcbde7f0f4a..32ec29460fa 100644
--- a/css-template-1/new2.html
+++ b/css-template-1/new2.html
@@ -3680,7 +3680,7 @@ <h2 id=chains><span class=secno>8. </span>Chaining slots: the &lsquo;<a
 </pre>
    </div>
 
-   <p class=note>Note: For more anaylysis of the possibilities and limits of
+   <p class=note>Note: For more analysis of the possibilities and limits of
     non-rectangular slots, see the PhD thesis of César Acebal <a
     href="#ACEBAL2010" rel=biblioentry>[ACEBAL2010]<!--{{ACEBAL2010}}--></a>.
     
diff --git a/css-template-1/new2.src.html b/css-template-1/new2.src.html
index a3f009ab6f8..40c36d711db 100644
--- a/css-template-1/new2.src.html
+++ b/css-template-1/new2.src.html
@@ -3027,7 +3027,7 @@ <h2 id=chains>Chaining slots: the 'chains' property</h2>
 </pre>
 </div>
 
-<p class=note>Note: For more anaylysis of the possibilities and limits
+<p class=note>Note: For more analysis of the possibilities and limits
 of non-rectangular slots, see the PhD thesis of César Acebal
 [[ACEBAL2010]].
 
diff --git a/css-text-3/Overview.bs b/css-text-3/Overview.bs
index 4a2657ea82f..bee277a5a08 100644
--- a/css-text-3/Overview.bs
+++ b/css-text-3/Overview.bs
@@ -279,7 +279,7 @@ Characters and Letters</h3>
   the relevant <a>character</a> unit depends on the operation.
   For example, line-breaking and letter-spacing will segment
   a sequence of Thai characters that include U+0E33 THAI CHARACTER SARA AM differently;
-  or the behaviour of a conjunct consonant in a script such as Devanagari
+  or the behavior of a conjunct consonant in a script such as Devanagari
   may depend on the font in use.
   So the <a>typographic character</a> represents a unit of the writing system&mdash;<!--
   -->such as a Latin alphabetic letter (including its diacritics),
@@ -654,7 +654,7 @@ Text Processing</h3>
     without affecting the semantics of the document.
     Note in particular that 'text-transform' casing operations are lossy,
     and can distort the meaning of a text.
-    While accessiblity interfaces may wish to convey
+    While accessibility interfaces may wish to convey
     the apparent casing of the rendered text to the user,
     the transformed text cannot be relied on to accurately represent
     the underlying meaning of the document.
@@ -1355,7 +1355,7 @@ Order of Operations</h4>
 	carriage returns (U+000D)
     and sequences that form a <a>segment break</a>--
     must be rendered as a visible glyph
-    which the UA must synthethize if the glyphs found in the font are not visible,
+    which the UA must synthesize if the glyphs found in the font are not visible,
     and must be otherwise treated as any other character
     of the Other Symbols (<code>So</code>) <a>general category</a> and Common <a lt="Unicode script">script</a>.
     The UA may use a glyph provided by a font specifically for the control character,
@@ -2300,7 +2300,7 @@ CUT SEGMENT BREAK TRANSFORM -->
       Note: Historically, HTML and CSS have unconditionally converted [=segment breaks=] to spaces,
       which has prevented content authored in languages such as Chinese
       from being able to break lines within the source.
-      Thus UA heurstics need to be conservative about where they discard [=segment breaks=]
+      Thus UA heuristics need to be conservative about where they discard [=segment breaks=]
       even as they strive to improve support for such languages.
 
   <h3 id="tab-size-property" caniuse="css3-tabsize" oldids="tab-size">
@@ -3331,7 +3331,7 @@ Line Breaking Details</h3>
         to be wrapped to the next line when 'white-space' is set to ''white-space/break-spaces'',
         because in other cases:
         * [=preserved white space=] at the end/start of the line is discarded (''white-space/normal'', ''white-space/pre-line'')
-        * wrapping is forbidden altoghether (''nowrap'', ''pre'')
+        * wrapping is forbidden altogether (''nowrap'', ''pre'')
         * the [=preserved white space=] [=hang=] (''pre-wrap'').
 
         When it does have an effect on [=preserved white space=],
@@ -4386,7 +4386,7 @@ Shaping Across Intra-word Breaks</h3>
           </wpt>
           <div class="figure" id="fig-text-justify-none">
             <p>
-              <img alt="No extra space is insesrted."
+              <img alt="No extra space is inserted."
                    src="images/text-justify-none.png"></p>
             <p class="caption">Mixed-script text with ''text-justify: none''
           </div>
@@ -4599,7 +4599,7 @@ Minimum Requirements for ''text-justify/auto'' Justification</h4>
     <li>
       All <a>letters</a> belonging to all <a>block scripts</a> are treated the same,
       and all <a>letters</a> belonging to all <a>clustered scripts</a> are treated the same.
-      For example, no distiction is made between
+      For example, no distinction is made between
       the justification opportunity between a Han letter followed by another Han letter,
       vs. the justification opportunity between a Han letter followed by a Hangul letter.
   </ul>
@@ -5259,7 +5259,7 @@ Cursive Scripts</h4>
     as they are not typical or fundamentally required
     by any modern writing system.
 
-    An example of impossible shaping accross boundaries
+    An example of impossible shaping across boundaries
     is a change in font weight partway through the word “and”
     in a font where a ligature would replace
     all three letters of the word “and”
@@ -5453,7 +5453,7 @@ Cursive Scripts</h4>
         </wpt>
 
         Note: This can lead to the element overflowing.
-        It is not recommended to use percentage indents and intrinsic sizing toghether.
+        It is not recommended to use percentage indents and intrinsic sizing together.
       </dd>
       <dt><dfn>each-line</dfn>
       <dd>Indentation affects the first line of each block container
diff --git a/css-text-3/test-coverage.html b/css-text-3/test-coverage.html
index ff9ce9c6d96..b805ca40895 100644
--- a/css-text-3/test-coverage.html
+++ b/css-text-3/test-coverage.html
@@ -31,7 +31,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="cont
 
 	<ul>
 		<li><a href="https://github.com/web-platform-tests/wpt/tree/master/css/css-text/">wpt/css/css-text/</a> and subdirectories
-		<li>All tests in <a href="https://github.com/web-platform-tests/wpt/tree/master/css/CSS2/">wpt/css/CSS2/</a> and subdirectories that relate to ththis specification.
+		<li>All tests in <a href="https://github.com/web-platform-tests/wpt/tree/master/css/CSS2/">wpt/css/CSS2/</a> and subdirectories that relate to this specification.
 		<li><a href="https://github.com/web-platform-tests/wpt/tree/master/css/vendor-imports/mozilla/mozilla-central-reftests/text3">wpt/css/vendor-imports/mozilla/mozilla-central-reftests/text3/</a>
 	</ul>
 
@@ -48,7 +48,7 @@ <h2 class="no-num no-toc no-ref heading settled" id="abstract"><span class="cont
 
 <hr>
 
-<h2 id=overall>Throughough the spec</h2>
+<h2 id=overall>Throughout the spec</h2>
 
 <p>Tests for <a href=https://github.com/w3c/csswg-drafts/issues/5303>distinguishing between applying to inlines and applying to text</a> should be added.
 
@@ -115,7 +115,7 @@ <h3 id="case-transforms-the-text-transform-property">2.1 <a href="https://drafts
 
 <h2 id="white-space-and-wrapping-the-white-space-property">3 <a href="https://drafts.csswg.org/css-text-3/#white-space-property">White Space and Wrapping: the white-space property</a></h2>
 
-<p>Good overal coverage through section 4 (white space processing details) and subsections.
+<p>Good overall coverage through section 4 (white space processing details) and subsections.
 
 <p>Missing tests:
 
diff --git a/css-text-4/Overview.bs b/css-text-4/Overview.bs
index f89cc027af8..2913147d169 100644
--- a/css-text-4/Overview.bs
+++ b/css-text-4/Overview.bs
@@ -202,7 +202,7 @@ Detecting Word Boundaries: the 'word-boundary-detection' property</h4>
 			If the UA does not support word-boundary detection
 			for <em>all</em> languages represented by the specified range,
 			that specified value is invalid
-			(and will cause the declaration to be ingored).
+			(and will cause the declaration to be ignored).
 
 			<wpt>
 				css/css-text/word-boundary/word-boundary-105.html
@@ -330,7 +330,7 @@ Detecting Word Boundaries: the 'word-boundary-detection' property</h4>
 
 		Authors who prepare their content in this manner
 		should not rely on the initial value, and
-		should explicitely specify ''word-boundary-detection: manual'' on the relevant parts of the content,
+		should explicitly specify ''word-boundary-detection: manual'' on the relevant parts of the content,
 		in order to override a potential ''word-boundary-detection: auto(<<lang>>)''
 		in the [=User Origin=] or [=User Agent Origin=].
 	</div>
@@ -393,7 +393,7 @@ Detecting Word Boundaries: the 'word-boundary-detection' property</h4>
 		<pre><code highlight=html>กรุงเทพ<span style="color:red">|</span>คือ<span style="color:red">|</span>&lt;em>สวยงาม&lt;/em></code></pre>
 		The following example shows <em>incorrect</em> positions:
 		<pre><code highlight=html>กรุงเทพ<span style="color:red">|</span>คือ&lt;em><span style="color:red">|</span>สวยงาม&lt;/em></code></pre>
-		The following shows the correct positions in a more contrieved situation:
+		The following shows the correct positions in a more contrived situation:
 		<pre><code highlight=html>กรุงเทพ<span style="color:red">|</span>&lt;b>&lt;u>คือ&lt;/u><span style="color:red">|</span>&lt;em>สวยงาม&lt;/em>&lt;/b></code></pre>
 	</div>
 
@@ -444,7 +444,7 @@ Detecting Word Boundaries: the 'word-boundary-detection' property</h4>
 
 		<li>
 			between a [=typographic letter unit=]
-			and a preceeding [=typographic character unit=] from the [[!UAX14]] OP line break class,
+			and a preceding [=typographic character unit=] from the [[!UAX14]] OP line break class,
 
 			<wpt>
 				css/css-text/word-boundary/word-boundary-126.html
@@ -474,7 +474,7 @@ Detecting Word Boundaries: the 'word-boundary-detection' property</h4>
 
 		<li>
 			between a [=typographic letter unit=]
-			and a preceeding [=typographic character unit=] from the [[!UAX14]] PR line break class,
+			and a preceding [=typographic character unit=] from the [[!UAX14]] PR line break class,
 
 			<wpt>
 				css/css-text/word-boundary/word-boundary-129.html
@@ -514,7 +514,7 @@ Makig Word Boundaries Visible: the 'word-boundary-expansion' property</h4>
 
 	This property allows transforming certain word-separating characters
 	into other word-separating characters,
-	to accomodate variant typesetting styles.
+	to accommodate variant typesetting styles.
 
 	<dl dfn-for="word-boundary-expansion" dfn-type="value">
 		<dt><dfn>none</dfn>
diff --git a/css-text-decor-4/Overview.bs b/css-text-decor-4/Overview.bs
index 10d30a9086e..727e0c09f97 100644
--- a/css-text-decor-4/Overview.bs
+++ b/css-text-decor-4/Overview.bs
@@ -427,7 +427,7 @@ Determining the Position and Thickness of Line Decorations</h3>
 				This can produce some undesirable jumpiness,
 				but there doesn't appear to be any way to avoid that which is correct in all instances,
 				and all attempts are worryingly complex.
-				What position should line-throughts adopt over elements that have a different font-size,
+				What position should line-throughs adopt over elements that have a different font-size,
 				but no <a>considered text</a>?
 	</dl>
 
@@ -2110,7 +2110,7 @@ Changes since the 13 March 2018 Working Draft</h3>
 	<li>Renamed <css>text-decoration-width</css> to 'text-decoration-thickness'.
 	<li>Added <<percentage>> values to 'text-decoration-thickness' and 'text-underline-offset'.
 		(<a href="https://github.com/w3c/csswg-drafts/issues/2165">Issue 2165</a>)
-	<li>Defined 'text-underline-offset' postion values as outsets rather than insets,
+	<li>Defined 'text-underline-offset' position values as outsets rather than insets,
 		because this was more intuitive to users.
 	<li>Moved ''text-underline-position/from-font'' keyword from 'text-underline-offset' to 'text-underline-position'.
 		(<a href="https://github.com/w3c/csswg-drafts/issues/3118#issuecomment-432297480">Issue 3118</a>)
diff --git a/css-transforms-1/ChangeLog b/css-transforms-1/ChangeLog
index 0e8e8eaccfd..d291da394d6 100755
--- a/css-transforms-1/ChangeLog
+++ b/css-transforms-1/ChangeLog
@@ -46,7 +46,7 @@
     https://www.w3.org/Bugs/Public/show_bug.cgi?id=25134
 
 2014-02-01 Dirk Schulze <dschulze@adobe.com>
-    Extend defintion for user space on use and export it.
+    Extend definition for user space on use and export it.
 
 2014-01-26 Simon Fraser <simon.fraser@apple.com>
     Provide an anchor for attributeName to keep bikeshed happy.
@@ -56,7 +56,7 @@
     
 2014-01-25 Simon Fraser <simon.fraser@apple.com>
     Change to note that transforms do affect getClientRects() and 
-    getBoundingClientRect(), and add a paragraph to the Module Interations
+    getBoundingClientRect(), and add a paragraph to the Module Interactions
     section about his.
     
     Also change wording of the note on transforms not affecting layout,
@@ -71,7 +71,7 @@
 
 2013-10-10  Dirk Schulze  <dschulze@adobe.com>
     Differ between 2D and 3D matrix decomposing.
-    Add defintions for a 2D matrix and a 3D matrix.
+    Add definitions for a 2D matrix and a 3D matrix.
     Decomposing code for 2D will be added with ono of
     the next commits.
 
@@ -109,7 +109,7 @@
     Add conformance section.
 
 2012-11-13 dschulze@adobe.com
-    Add defintions for keywords on 'transform-origin' and 'perspective-origin'.
+    Add definitions for keywords on 'transform-origin' and 'perspective-origin'.
 
 2012-11-05 dschulze@adobe.com
     Clarify multiplication order.
@@ -132,7 +132,7 @@
     Fixed typo.
 
 2012-10-19 dschulze@adobe.com
-    Correction on transformable elements defintion.
+    Correction on transformable elements definition.
     Remove all uses of 'In HTML namespace'.
 
 2012-10-19 dschulze@adobe.com
@@ -160,7 +160,7 @@
     Corrected typo.
 
 2012-08-9 dschulze@adobe.com
-    Simplify transform interpolation uppen request of CSS WG.
+    Simplify transform interpolation upon request of CSS WG.
     rotate3d still gets decomposed as 4x4matrix for now.
 
 2012-07-27 dschulze@adobe.com
@@ -170,7 +170,7 @@
     Transform lists get no longer premultiplied if some functions in the list
     are of type 'matrix', 'rotate3d', 'rotateX', 'rotateY', 'rotateZ', 'matrix3d'
     and ‘perspective’. 
-    Instead 'rotateX', 'rotateY' and 'rotateZ' get interpolated numericaly and
+    Instead 'rotateX', 'rotateY' and 'rotateZ' get interpolated numerically and
     'matrix', 'rotate3d' and ‘perspective’ get converted to matrix4x4 and
     interpolated as matrices. 
 
@@ -180,7 +180,7 @@
     ‘gradientUnit’ and ‘maskUnit’ attributes. Theses attributes just affect 'x',
     'y', 'width' and 'height'.
     Added an issue if percentage should be dependent on viewport or the bounding
-    box of the referencin object.
+    box of the referencing object.
 
 2012-07-12 simon.fraser@apple.com
     Fix https://www.w3.org/Bugs/Public/show_bug.cgi?id=17431 by making the wording
diff --git a/css-transforms-1/Overview.bs b/css-transforms-1/Overview.bs
index 654295bfb3f..07ae2a598f5 100644
--- a/css-transforms-1/Overview.bs
+++ b/css-transforms-1/Overview.bs
@@ -289,7 +289,7 @@ The 'transform-origin' property moves the point of origin by 50 pixels in both t
   }
   </code></pre>
 
-The visual appareance is as if the <a element>div</a> element gets translated by 80px to the bottom left direction, then scaled up by 150% and finally rotated by 45&deg;.
+The visual appearance is as if the <a element>div</a> element gets translated by 80px to the bottom left direction, then scaled up by 150% and finally rotated by 45&deg;.
 
 Each <<transform-function>> can get represented by a corresponding 4x4 matrix. To map a point from the coordinate space of the <a element>div</a> box to the coordinate space of the parent element, these transforms get multiplied in the reverse order:
 1. The rotation matrix gets <a>post-multiplied</a> by the scale matrix.
@@ -320,7 +320,7 @@ For elements whose layout is governed by the CSS box model, any value other than
 For elements whose layout is governed by the CSS box model, any value other than ''transform/none'' for the 'transform' property also causes the element to establish a <dfn export>containing block for all descendants</dfn>. Its padding box will be used to layout for all of its absolute-position descendants, fixed-position descendants, and descendant fixed background attachments.
 
 <div class="example">
-To demostrate the effect of [=containing block for all descendants=] on fixed-position descendants, the following code snippets should behave identically:
+To demonstrate the effect of [=containing block for all descendants=] on fixed-position descendants, the following code snippets should behave identically:
 <pre><code highlight=html>
 &lt;style>
 #container {
diff --git a/css-transforms-1/issues-wd-2013.html b/css-transforms-1/issues-wd-2013.html
index f0178714136..c201e49dec7 100644
--- a/css-transforms-1/issues-wd-2013.html
+++ b/css-transforms-1/issues-wd-2013.html
@@ -421,7 +421,7 @@ <h1>CSS Transforms Level 1 Disposition of Comments for 2013-11-26 WD</h1>
 <span>Resolved: <a href='https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html'>https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html</a></span></pre>
 <pre class='open ' id='issue-46'>
 <span>Issue 46. <a href='#issue-46'>#</a></span>
-<span>Summary:  transform-box values & correspondance to SVG vs CSS</span>
+<span>Summary:  transform-box values & correspondence to SVG vs CSS</span>
 <span>From:     Erik Dahlström</span>
 <span>Comment:  <a href='https://www.w3.org/mid/op.x5otn9g7fwt8au@localhost.localdomain'>https://www.w3.org/mid/op.x5otn9g7fwt8au@localhost.localdomain</a></span>
 <span>Response: <a href='https://github.com/w3c/csswg-drafts/issues/928'>https://github.com/w3c/csswg-drafts/issues/928</a></span>
diff --git a/css-transforms-1/issues-wd-2013.txt b/css-transforms-1/issues-wd-2013.txt
index 3df9bc1ed52..40ed9f1d801 100644
--- a/css-transforms-1/issues-wd-2013.txt
+++ b/css-transforms-1/issues-wd-2013.txt
@@ -409,7 +409,7 @@ Open:     =ED= Transfer to Geometry per WG resolution
 Resolved: https://lists.w3.org/Archives/Public/www-style/2017Feb/0054.html
 ----
 Issue 46.
-Summary:  transform-box values & correspondance to SVG vs CSS
+Summary:  transform-box values & correspondence to SVG vs CSS
 From:     Erik Dahlström
 Comment:  https://www.w3.org/mid/op.x5otn9g7fwt8au@localhost.localdomain
 Response: https://github.com/w3c/csswg-drafts/issues/928
diff --git a/css-transforms-1/test/Overview.html b/css-transforms-1/test/Overview.html
index d4dd5758c40..99f92d4ab05 100644
--- a/css-transforms-1/test/Overview.html
+++ b/css-transforms-1/test/Overview.html
@@ -584,7 +584,7 @@ <h2 class="heading settled" data-level="3" id="transform-rendering"><span class=
   <c- k>transform</c-><c- p>:</c-> <c- nf>translate</c-><c- p>(</c-><c- m>80</c-><c- l>px</c-><c- p>,</c-> <c- m>80</c-><c- l>px</c-><c- p>)</c-> <c- nf>scale</c-><c- p>(</c-><c- m>1.5</c-><c- p>,</c-> <c- m>1.5</c-><c- p>)</c-> <c- nf>rotate</c-><c- p>(</c-><c- m>45</c-><c- l>deg</c-><c- p>);</c->
 <c- p>}</c->
 </code></pre>
-    <p>The visual appareance is as if the <a data-link-type="element" href="https://html.spec.whatwg.org/multipage/grouping-content.html#the-div-element" id="ref-for-the-div-element">div</a> element gets translated by 80px to the bottom left direction, then scaled up by 150% and finally rotated by 45°.</p>
+    <p>The visual appearance is as if the <a data-link-type="element" href="https://html.spec.whatwg.org/multipage/grouping-content.html#the-div-element" id="ref-for-the-div-element">div</a> element gets translated by 80px to the bottom left direction, then scaled up by 150% and finally rotated by 45°.</p>
     <p>Each <a class="production css" data-link-type="type" href="#typedef-transform-function" id="ref-for-typedef-transform-function①">&lt;transform-function></a> can get represented by a corresponding 4x4 matrix. To map a point from the coordinate space of the <a data-link-type="element" href="https://html.spec.whatwg.org/multipage/grouping-content.html#the-div-element" id="ref-for-the-div-element①">div</a> box to the coordinate space of the parent element, these transforms get multiplied in the reverse order:</p>
     <ol>
      <li data-md>
@@ -608,7 +608,7 @@ <h2 class="heading settled" data-level="3" id="transform-rendering"><span class=
    <p>For elements whose layout is governed by the CSS box model, any value other than <span class="css">none</span> for the <a class="property" data-link-type="propdesc" href="#propdef-transform" id="ref-for-propdef-transform⑧">transform</a> property results in the creation of a stacking context. Implementations must paint the layer it creates, within its parent stacking context, at the same stacking order that would be used if it were a positioned element with <a class="css" data-link-type="propdesc" href="https://www.w3.org/TR/css3-positioning/#propdef-z-index" id="ref-for-propdef-z-index">z-index: 0</a>. If an element with a transform is positioned, the <a class="property" data-link-type="propdesc" href="https://www.w3.org/TR/css3-positioning/#propdef-z-index" id="ref-for-propdef-z-index①">z-index</a> property applies as described in <a data-link-type="biblio" href="#biblio-css2">[CSS2]</a>, except that <a class="css" data-link-type="maybe" href="https://www.w3.org/TR/css3-positioning/#valdef-z-index-auto" id="ref-for-valdef-z-index-auto">auto</a> is treated as <span class="css">0</span> since a new stacking context is always created.</p>
    <p>For elements whose layout is governed by the CSS box model, any value other than <span class="css">none</span> for the <a class="property" data-link-type="propdesc" href="#propdef-transform" id="ref-for-propdef-transform⑨">transform</a> property also causes the element to establish a <dfn class="dfn-paneled" data-dfn-type="dfn" data-export id="containing-block-for-all-descendants">containing block for all descendants</dfn>. Its padding box will be used to layout for all of its absolute-position descendants, fixed-position descendants, and descendant fixed background attachments.</p>
    <div class="example" id="example-02d1d5ba">
-    <a class="self-link" href="#example-02d1d5ba"></a> To demostrate the effect of <a data-link-type="dfn" href="#containing-block-for-all-descendants" id="ref-for-containing-block-for-all-descendants">containing block for all descendants</a> on fixed-position descendants, the following code snippets should behave identically: 
+    <a class="self-link" href="#example-02d1d5ba"></a> To demonstrate the effect of <a data-link-type="dfn" href="#containing-block-for-all-descendants" id="ref-for-containing-block-for-all-descendants">containing block for all descendants</a> on fixed-position descendants, the following code snippets should behave identically: 
 <pre><code class="highlight"><c- p>&lt;</c-><c- f>style</c-><c- p>></c->
 <c- p>#</c-><c- nn>container</c-> <c- p>{</c->
   <c- k>width</c-><c- p>:</c-> <c- mi>300</c-><c- b>px</c-><c- p>;</c->
diff --git a/css-transforms-2/Overview.bs b/css-transforms-2/Overview.bs
index b480a616d68..eb4d4058c16 100644
--- a/css-transforms-2/Overview.bs
+++ b/css-transforms-2/Overview.bs
@@ -170,7 +170,7 @@ Authors can easily provide a fallback if UAs do not provide support for three-di
 The Transform Rendering Model {#transform-rendering}
 ====================================================
 
-This specification extends [[css-transforms-1#transform-rendering]] to account for the existence of three-dimensional transform functions, the Z value of 'transform-orign', the 'perspective' property, and a new 3D rendering model that applies when the used value of the ''transform-style'' property is ''transform-style/preserve-3d''.
+This specification extends [[css-transforms-1#transform-rendering]] to account for the existence of three-dimensional transform functions, the Z value of 'transform-origin', the 'perspective' property, and a new 3D rendering model that applies when the used value of the ''transform-style'' property is ''transform-style/preserve-3d''.
 
 Three-dimensional transform functions conceptually extend the coordinate space into three dimensions, adding a Z axis perpendicular to the plane of the screen, that increases towards the viewer.
 
@@ -308,8 +308,8 @@ Elements establish and participate in 3D rendering contexts as follows:
 Some CSS properties have values that are considered to force "grouping": they require that their element and its descendants are rendered as a group before being composited with other elements; these include opacity, filters and properties that affect clipping. The relevant property values are listed under <a href="#grouping-property-values">grouping property values</a>. Consequently, when used on an element with transform-style:preserve-3d, they change the used value to
 ''transform-style/flat'' and prevent it from creating or extending a <a>3D rendering context</a>.
 
-Issue: This doesn't describe how untransformed content within a 3D transformed element is handled, the alogrithm probably needs to be recursive.
-Issue: Figure out what the current behaviour of various engines is, and figure out a clearer description that wont break web compat.
+Issue: This doesn't describe how untransformed content within a 3D transformed element is handled, the algorithm probably needs to be recursive.
+Issue: Figure out what the current behavior of various engines is, and figure out a clearer description that wont break web compat.
 
 The rendering of elements in a 3D rendering context is as follows (numbers refer to items in <a href="https://www.w3.org/TR/CSS2/zindex.html#painting-order">CSS 2.1, Appendix E, Section E.2 Painting Order</a>):
 
diff --git a/css-transitions-1/use-cases.html b/css-transitions-1/use-cases.html
index b5333418008..860b0e86487 100644
--- a/css-transitions-1/use-cases.html
+++ b/css-transitions-1/use-cases.html
@@ -545,7 +545,7 @@ <h1>Use cases for transitions/animations/effects</h1>
 
 <td>3b: Same as 3a, but also play the 'bounce' animation when the class of the element is changed back from "two" to "one", while the element is moved back to its original position.
 
-<tr><td>3c: Same as 3b, but play the 'sway' animation (which takes 2s to run) continously between the two 'bounce' animations.
+<tr><td>3c: Same as 3b, but play the 'sway' animation (which takes 2s to run) continuously between the two 'bounce' animations.
 
 <td>not possible in CSS
 <td>
@@ -642,7 +642,7 @@ <h1>Use cases for transitions/animations/effects</h1>
 </pre>
 
 
-<td>3c: Same as 3b, but play the 'sway' animation (which takes 2s to run) continously between the two 'bounce' animations.
+<td>3c: Same as 3b, but play the 'sway' animation (which takes 2s to run) continuously between the two 'bounce' animations.
 </table>
 
 <h2 id=effect>The 'effect' property</h2>
diff --git a/css-ui-3/Overview.bs b/css-ui-3/Overview.bs
index 24a332a164a..21b4cef6461 100644
--- a/css-ui-3/Overview.bs
+++ b/css-ui-3/Overview.bs
@@ -78,7 +78,7 @@ spec:css2; type:property; text:border-width
 spec:css2; type:property; text:background-image
 </pre>
 
-<!-- Some of the following definitions have existing exported defintions from other specs,
+<!-- Some of the following definitions have existing exported definitions from other specs,
 but not from specs that are OK to link to from a CR -->
 <pre class="anchors">
 url: https://www.w3.org/TR/CSS2/box.html#border-edge; type: dfn; spec: CSS2; text: border edge
@@ -609,7 +609,7 @@ with no other constraints than what is imposed by
 'min-width', 'max-width', 'min-height', and 'max-height'.
 
 Note: There may be situations where user attempts to resize an element
-appear to be overriden or ignored, e.g. because of ''!important'' cascading declarations that supersede
+appear to be overridden or ignored, e.g. because of ''!important'' cascading declarations that supersede
 that element’s <a href="https://www.w3.org/TR/css-style-attr/#style-attribute">style attribute</a>
 'width' and 'height' properties in the DOM.
 
diff --git a/css-ui-3/implementation-report.html b/css-ui-3/implementation-report.html
index 0b968ac4931..70928c8ff04 100644
--- a/css-ui-3/implementation-report.html
+++ b/css-ui-3/implementation-report.html
@@ -190,7 +190,7 @@ <h3 id=summary><a href="#summary" class=self-link></a>Summary</h3>
 <h3 id=analysis><a href="#analysis" class=self-link></a>Detailed Analysis</h3>
 
 <p>This section discusses the <strong>cases where while CR exit criteria are met</strong>,
-various factors suggest closer inspecition may be in order,
+various factors suggest closer inspection may be in order,
 and explain the reason why these <strong>concerns are ultimately not warranted</strong>.
 
 
diff --git a/css-ui-3/issues-2012-2015.html b/css-ui-3/issues-2012-2015.html
index 36533112871..571c0f87ac7 100644
--- a/css-ui-3/issues-2012-2015.html
+++ b/css-ui-3/issues-2012-2015.html
@@ -517,7 +517,7 @@ <h1>CSS Basic User Interface Module Level 3 (CSS3 UI) Disposition of Comments fo
 Closed: Accepted</pre>
 <pre class='a' id='issue-53'>
 Issue 53. <a href='#issue-53'>#</a>
-Summary: resize factor behaviour is weird when width / height are later dynamically modified
+Summary: resize factor behavior is weird when width / height are later dynamically modified
 From: Lea Verou
 Comment: <a href='http://lists.w3.org/Archives/Public/www-style/2014Jul/0517.html'>http://lists.w3.org/Archives/Public/www-style/2014Jul/0517.html</a>
 ; URL : <a href='http://lists.w3.org/Archives/Public/www-style/2014Dec/0063.html'>http://lists.w3.org/Archives/Public/www-style/2014Dec/0063.html</a>
@@ -909,7 +909,7 @@ <h1>CSS Basic User Interface Module Level 3 (CSS3 UI) Disposition of Comments fo
 Comment: <a href='http://www.w3.org/mid/CACsW8eEQVD9K48FMt0UR7=c7S1=3LmX=itcnfc8UNE6WPRsBGg@mail.gmail.com'>http://www.w3.org/mid/CACsW8eEQVD9K48FMt0UR7=c7S1=3LmX=itcnfc8UNE6WPRsBGg@mail.gmail.com</a>
 Response: <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0111.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0111.html</a>
 Closed: Rejected
-Resolved: Editors' discression
+Resolved: Editors' discretion
 Verified: <a href='https://lists.w3.org/Archives/Public/www-style/2015Jun/0366.html'>https://lists.w3.org/Archives/Public/www-style/2015Jun/0366.html</a>
 Note: Reject, this is already stated 2 lines above.</pre>
 <pre class='a' id='issue-99'>
diff --git a/css-ui-3/issues-2012-2015.txt b/css-ui-3/issues-2012-2015.txt
index 2f18fb8b9f9..acafaed5e03 100644
--- a/css-ui-3/issues-2012-2015.txt
+++ b/css-ui-3/issues-2012-2015.txt
@@ -539,7 +539,7 @@ Closed: Accepted
 
 ----
 Issue 53.
-Summary: resize factor behaviour is weird when width / height are later dynamically modified
+Summary: resize factor behavior is weird when width / height are later dynamically modified
 From: Lea Verou
 Comment: http://lists.w3.org/Archives/Public/www-style/2014Jul/0517.html
 ; URL : http://lists.w3.org/Archives/Public/www-style/2014Dec/0063.html
@@ -976,7 +976,7 @@ From: Timeless
 Comment: http://www.w3.org/mid/CACsW8eEQVD9K48FMt0UR7=c7S1=3LmX=itcnfc8UNE6WPRsBGg@mail.gmail.com
 Response: https://lists.w3.org/Archives/Public/www-style/2015Jun/0111.html
 Closed: Rejected
-Resolved: Editors' discression
+Resolved: Editors' discretion
 Verified: https://lists.w3.org/Archives/Public/www-style/2015Jun/0366.html
 Note: Reject, this is already stated 2 lines above.
 
diff --git a/css-ui-3/transition-cr-2017-11.md b/css-ui-3/transition-cr-2017-11.md
index 167baff3c77..748aa450c43 100644
--- a/css-ui-3/transition-cr-2017-11.md
+++ b/css-ui-3/transition-cr-2017-11.md
@@ -9,7 +9,7 @@ CSS Basic User Interface Module Level 3 (CSS3 UI)
 
 https://drafts.csswg.org/css-ui-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
 
@@ -60,7 +60,7 @@ is within the scope defined in the CSS WG's charter,
 
 The following normative reference to W3C documents is not yet at CR:
 
-* [CSS-COLOR-4](https://www.w3.org/TR/css-color-4/), in order to refer to a precise definition of a concept that exists implicitely since CSS21.
+* [CSS-COLOR-4](https://www.w3.org/TR/css-color-4/), in order to refer to a precise definition of a concept that exists implicitly since CSS21.
 
 <!-- Only relevant for the PR transition
 
diff --git a/css-ui-3/transition-pr-2017-11.md b/css-ui-3/transition-pr-2017-11.md
index 0091a45e491..0b0d5f5b607 100644
--- a/css-ui-3/transition-pr-2017-11.md
+++ b/css-ui-3/transition-pr-2017-11.md
@@ -9,7 +9,7 @@ CSS Basic User Interface Module Level 3 (CSS3 UI)
 
 https://drafts.csswg.org/css-ui-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
 
@@ -56,7 +56,7 @@ is within the scope defined in the CSS WG's charter,
 
 The following normative reference to W3C documents is not yet at CR:
 
-* [CSS-COLOR-4](https://www.w3.org/TR/css-color-4/), in order to refer to a precise definition of a concept that exists implicitely since CSS21.
+* [CSS-COLOR-4](https://www.w3.org/TR/css-color-4/), in order to refer to a precise definition of a concept that exists implicitly since CSS21.
 
 Additionally, the following normative references to W3C documents are at CR but not yet at PR:
 
diff --git a/css-ui-4/Overview.bs b/css-ui-4/Overview.bs
index c3f18b8d9e9..ea9a9ee6e89 100644
--- a/css-ui-4/Overview.bs
+++ b/css-ui-4/Overview.bs
@@ -1,10 +1,10 @@
 <!--
 Coding style convention in this file:
 * Use semantic line breaks (http://rhodesmill.org/brandon/2012/one-sentence-per-line/)
-* Tabs for indentation, spaces for allignment (http://lea.verou.me/2012/01/why-tabs-are-clearly-superior/)
+* Tabs for indentation, spaces for alignment (http://lea.verou.me/2012/01/why-tabs-are-clearly-superior/)
 * Use markdown paragraphs (empty lines between paragraphs) over <p> when practical
 * two empty lines above <h*>, one below <h*>, one between <hn> and <hn+1>
-* empty line between <ol>, <ul>, <table>, <div> and ajacent text
+* empty line between <ol>, <ul>, <table>, <div> and adjacent text
 * Don't close <p>, <li>, <dd>, <dt>, <tr>, <th>, or <td>
 * Indent the content and break line after the opening <li>, <dd>, <dt>, <td>, or <th> if it's more than 2 lines long
   or for lists where at least some elements are more than 2 lines long
@@ -555,7 +555,7 @@ with no other constraints than what is imposed by
 'min-width', 'max-width', 'min-height', and 'max-height'.
 
 Note: There may be situations in which user attempts to resize an element
-appear to be overriden or ignored, e.g. because of ''!important'' cascading declarations that supersede
+appear to be overridden or ignored, e.g. because of ''!important'' cascading declarations that supersede
 that element’s <a href="https://www.w3.org/TR/css-style-attr/#style-attribute">style attribute</a>
 'width' and 'height' properties in the DOM.
 
@@ -820,7 +820,7 @@ Values have the following meanings:
 			over elements in a vertical [=writing mode=].
 			Additionally, User Agents may take transforms (see [[CSS-TRANSFORMS-1]])
 			or other visual effects such as text on a path (See [[SVG2/text#TextLayoutPath]]),
-			when chosing between the horizontal or vertical text cursor,
+			when choosing between the horizontal or vertical text cursor,
 			and may display any angle of I-beam/cursor for text that is rendered at any particular angle.
 
 		<dt style="cursor:vertical-text"><dfn>vertical-text</dfn>
@@ -1733,7 +1733,7 @@ or maybe all values should map to ''user-select/text''.
 		The UA must allow selections to extend across this element,
 		and such selections must include the content of the element.
 
-		Note: At the time of writing, experimental implementations behave differently from eachother
+		Note: At the time of writing, experimental implementations behave differently from each other
 		about selections started outside and selections going into the element.
 		The behavior can be observed even on browsers that do not explicitly support ''user-select/contain''
 		by trying to select into a <{textarea}> or a contenteditable element.
@@ -2321,7 +2321,7 @@ the following normative changes have been made:
 
 <ul>
 	<li>Added details about form control specific rendering rules
-	<li>Clarify interaction between text-overflow and annonymous block containers
+	<li>Clarify interaction between text-overflow and anonymous block containers
 	<li>Require the ''cursor/pointer'' cursor for hyperlinks in all document formats
 	<li>Moved the 'box-sizing' and 'text-overflow' properties to [[CSS-SIZING-3]] and [[CSS-OVERFLOW-4]] respectively.
 	<li>Changed the requirement that the ''cursor/text'' cursor matches the writing mode from MAY to MUST
diff --git a/css-ui-4/issues-fpwd-2015.html b/css-ui-4/issues-fpwd-2015.html
index 5ed61db12fd..12687f6ded9 100644
--- a/css-ui-4/issues-fpwd-2015.html
+++ b/css-ui-4/issues-fpwd-2015.html
@@ -142,7 +142,7 @@ <h1>CSS Basic User Interface Module Level 4 Disposition of Comments for 2015-09-
 Verified: <a href='https://github.com/w3c/csswg-drafts/issues/1815#issuecomment-418936418'>https://github.com/w3c/csswg-drafts/issues/1815#issuecomment-418936418</a></pre>
 <pre class='a' id='issue-13'>
 Issue 13. <a href='#issue-13'>#</a>
-Summary:  Clarify effect of annonymous block container boxes on text-overflow
+Summary:  Clarify effect of anonymous block container boxes on text-overflow
 From:     Oriol Brufau
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/2595'>https://github.com/w3c/csswg-drafts/issues/2595</a>
 Response: <a href='https://github.com/w3c/csswg-drafts/issues/2595#issuecomment-386153703'>https://github.com/w3c/csswg-drafts/issues/2595#issuecomment-386153703</a>
diff --git a/css-ui-4/issues-fpwd-2015.txt b/css-ui-4/issues-fpwd-2015.txt
index de2e837210c..515444a4b43 100644
--- a/css-ui-4/issues-fpwd-2015.txt
+++ b/css-ui-4/issues-fpwd-2015.txt
@@ -112,7 +112,7 @@ Resolved: https://github.com/w3c/csswg-drafts/issues/1815#issuecomment-418918926
 Verified: https://github.com/w3c/csswg-drafts/issues/1815#issuecomment-418936418
 ----
 Issue 13.
-Summary:  Clarify effect of annonymous block container boxes on text-overflow
+Summary:  Clarify effect of anonymous block container boxes on text-overflow
 From:     Oriol Brufau
 Comment:  https://github.com/w3c/csswg-drafts/issues/2595
 Response: https://github.com/w3c/csswg-drafts/issues/2595#issuecomment-386153703
diff --git a/css-writing-modes-3/Overview.bs b/css-writing-modes-3/Overview.bs
index 41161dbe1ae..c02cfc50f58 100644
--- a/css-writing-modes-3/Overview.bs
+++ b/css-writing-modes-3/Overview.bs
@@ -2557,7 +2557,7 @@ Privacy and Security Considerations {#priv-sec}
         (<a href="https://github.com/w3c/csswg-drafts/issues/3066">Issue 3066</a>)
     <li>Make the processing of white space
         in a 'text-combine-upright' combined text sequence
-        explicitely undefined in this level
+        explicitly undefined in this level
         (<a href="https://github.com/w3c/csswg-drafts/issues/4139">Issue 4139</a>)
         <blockquote>
           <p>When combining text as for ''text-combine-upright: all'',
@@ -2613,7 +2613,7 @@ Privacy and Security Considerations {#priv-sec}
       consistent with how CSS aliases are handled (see 'page-break-inside' for an example).
     <li>
       Added handling of degrees as integers in 'glyph-orientation-vertical',
-      as required for SVG backwards-compatiblity.
+      as required for SVG backwards-compatibility.
     <li>
       Removed statements about ''run-in'' boxes, since this value was removed from CSS2.1 and has a substantially different model in CSS Display Level 3.
       Replaced with a generalized statement about all display types, using new [[!CSS-DISPLAY-3]] terminology.
@@ -2706,6 +2706,6 @@ Vertical Scripts in Unicode</h2>
     rotation from this orientation.
 
   <p class="note">
-    Due to limitations in the current featureset of Unicode Technical Report 50 and CSS Writing Modes,
+    Due to limitations in the current feature set of Unicode Technical Report 50 and CSS Writing Modes,
     vertical ''mixed'' typesetting cannot automatically handle either Ogham or Old Turkic.
     For these scripts, ''sideways-lr'' (in <a href="http://www.w3.org/TR/css-writing-modes-4/">CSS Writing Modes Level 4</a>) can be used to typeset passages.
diff --git a/css-writing-modes-3/implementation-report-2019-08.html b/css-writing-modes-3/implementation-report-2019-08.html
index 27d26377537..d68a85cb8a5 100644
--- a/css-writing-modes-3/implementation-report-2019-08.html
+++ b/css-writing-modes-3/implementation-report-2019-08.html
@@ -91,7 +91,7 @@ <h3 id=summary><a href="#summary" class=self-link></a>1.1. Summary</h3>
 
 <ul>
 	<li>
-		The success criteria established in the working group charter speficy that
+		The success criteria established in the working group charter specify that
 		<q>In order to advance to Proposed Recommendation,
 			each module is expected to have at least two independent implementations
 			of each of feature defined in the specification</q>.
diff --git a/css-writing-modes-3/issues-cr-2015.html b/css-writing-modes-3/issues-cr-2015.html
index 2c0c340c674..cd1617e2af0 100644
--- a/css-writing-modes-3/issues-cr-2015.html
+++ b/css-writing-modes-3/issues-cr-2015.html
@@ -245,7 +245,7 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2015-12-15 CR</h1>
 Response: <a href='https://lists.w3.org/Archives/Public/www-style/2018Jan/0074.html'>https://lists.w3.org/Archives/Public/www-style/2018Jan/0074.html</a>
 Comment:  <a href='https://lists.w3.org/Archives/Public/www-style/2018Jan/0081.html'>https://lists.w3.org/Archives/Public/www-style/2018Jan/0081.html</a>
 Closed:   Rejected
-Resolved: Editor discression</pre>
+Resolved: Editor discretion</pre>
 <script>
 (function () {
     var sheet = document.styleSheets[0];
diff --git a/css-writing-modes-3/issues-cr-2015.txt b/css-writing-modes-3/issues-cr-2015.txt
index a7f09664ef5..e264ba5aca5 100644
--- a/css-writing-modes-3/issues-cr-2015.txt
+++ b/css-writing-modes-3/issues-cr-2015.txt
@@ -217,4 +217,4 @@ Comment:  https://lists.w3.org/Archives/Public/www-style/2018Jan/0064.html
 Response: https://lists.w3.org/Archives/Public/www-style/2018Jan/0074.html
 Comment:  https://lists.w3.org/Archives/Public/www-style/2018Jan/0081.html
 Closed:   Rejected
-Resolved: Editor discression
+Resolved: Editor discretion
diff --git a/css-writing-modes-3/issues-cr-2018.html b/css-writing-modes-3/issues-cr-2018.html
index 463c0530a32..9f0a62dcfd3 100644
--- a/css-writing-modes-3/issues-cr-2018.html
+++ b/css-writing-modes-3/issues-cr-2018.html
@@ -79,7 +79,7 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3260'>https://github.com/w3c/csswg-drafts/issues/3260</a>
 Response: <a href='https://github.com/w3c/csswg-drafts/issues/3260#issuecomment-495363659'>https://github.com/w3c/csswg-drafts/issues/3260#issuecomment-495363659</a>
 Closed:   OutOfScope
-Resolved: Editor's discression</pre>
+Resolved: Editor's discretion</pre>
 <pre class='d' id='issue-7'>
 Issue 7. <a href='#issue-7'>#</a>
 Summary:  Improve old diagram in figure
@@ -112,7 +112,7 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/3505'>https://github.com/w3c/csswg-drafts/issues/3505</a>
 Response: <a href='https://github.com/w3c/svgwg/issues/629'>https://github.com/w3c/svgwg/issues/629</a>
 Closed:   OutOfScope
-Resolved: Editor's discression (<a href='https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)'>https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)</a>
+Resolved: Editor's discretion (<a href='https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)'>https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)</a>
 Verified: <a href='https://github.com/w3c/svgwg/issues/629#issuecomment-493824657'>https://github.com/w3c/svgwg/issues/629#issuecomment-493824657</a></pre>
 <pre class='a' id='issue-11'>
 Issue 11. <a href='#issue-11'>#</a>
@@ -141,7 +141,7 @@ <h1>CSS Writing Modes Level 3 Disposition of Comments for 2018-05-24 CR</h1>
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511995790'>https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511995790</a>
 Response: <a href='https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-513586713'>https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-513586713</a>
 Closed:   OutOfScope
-Resolved: Editor's discression
+Resolved: Editor's discretion
 Verified: <a href='https://github.com/w3c/csswg-drafts/issues/4033#event-2498263624'>https://github.com/w3c/csswg-drafts/issues/4033#event-2498263624</a></pre>
 <script>
 (function () {
diff --git a/css-writing-modes-3/issues-cr-2018.txt b/css-writing-modes-3/issues-cr-2018.txt
index b9a955e4ee0..075c1dc62d9 100644
--- a/css-writing-modes-3/issues-cr-2018.txt
+++ b/css-writing-modes-3/issues-cr-2018.txt
@@ -51,7 +51,7 @@ From:     prjnt
 Comment:  https://github.com/w3c/csswg-drafts/issues/3260
 Response: https://github.com/w3c/csswg-drafts/issues/3260#issuecomment-495363659
 Closed:   OutOfScope
-Resolved: Editor's discression
+Resolved: Editor's discretion
 ----
 Issue 7.
 Summary:  Improve old diagram in figure
@@ -84,7 +84,7 @@ From:     Evgeniy Reizner
 Comment:  https://github.com/w3c/csswg-drafts/issues/3505
 Response: https://github.com/w3c/svgwg/issues/629
 Closed:   OutOfScope
-Resolved: Editor's discression (https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)
+Resolved: Editor's discretion (https://github.com/w3c/csswg-drafts/issues/3505#issuecomment-454236964)
 Verified: https://github.com/w3c/svgwg/issues/629#issuecomment-493824657
 ----
 Issue 11.
@@ -113,5 +113,5 @@ Comment:  https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511993353
 Comment:  https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-511995790
 Response: https://github.com/w3c/csswg-drafts/issues/4033#issuecomment-513586713
 Closed:   OutOfScope
-Resolved: Editor's discression
+Resolved: Editor's discretion
 Verified: https://github.com/w3c/csswg-drafts/issues/4033#event-2498263624
diff --git a/css-writing-modes-4/Overview.bs b/css-writing-modes-4/Overview.bs
index 02ee81b0389..c30580f83d7 100644
--- a/css-writing-modes-4/Overview.bs
+++ b/css-writing-modes-4/Overview.bs
@@ -2922,6 +2922,6 @@ Vertical Scripts in Unicode</h2>
     rotation from this orientation.
 
   <p class="note">
-    Due to limitations in the current featureset of Unicode Technical Report 50 and CSS Writing Modes,
+    Due to limitations in the current feature set of Unicode Technical Report 50 and CSS Writing Modes,
     vertical ''mixed'' typesetting cannot automatically handle either Ogham or Old Turkic.
     For these scripts, ''sideways-lr'' can be used to typeset passages.
diff --git a/css2/Overview.bs b/css2/Overview.bs
index 570f4298325..de20b5c3241 100644
--- a/css2/Overview.bs
+++ b/css2/Overview.bs
@@ -5049,7 +5049,7 @@ nonetheless valid identifiers) are treated as if the unknown media
 types are not present. If an @media/@import rule contains a malformed
 media type (not an identifier) then the statement is invalid.
 
-<p class="note"><em><strong>Note:</strong> Media Queries supercedes this
+<p class="note"><em><strong>Note:</strong> Media Queries supersedes this
 error handling.</em>
 
 <div class="example">
diff --git a/css3-tables-algorithms/Overview.src.htm b/css3-tables-algorithms/Overview.src.htm
index 54316d486ee..b663bc38ce7 100644
--- a/css3-tables-algorithms/Overview.src.htm
+++ b/css3-tables-algorithms/Overview.src.htm
@@ -639,7 +639,7 @@ <h1 ><span >1.</span><span
 </span>Cell Intrinsic Min width (cellIntrinsicMinWidth) and Cell Intrinsic
 Preferred Width (<span >cellIntrinsicPreferredWidth</span>)</b></p>
 
-<p class=MsoListParagraph >cellIntrinsicMinWidth and cellIntrinsicPreferedWidth
+<p class=MsoListParagraph >cellIntrinsicMinWidth and cellIntrinsicPreferredWidth
 should be calculated based on the regular CSS2.1 shrink to fit block model
 calculations (see sections 10.3.5 and 10.3.7 for further details).</p>
 
@@ -717,7 +717,7 @@ <h1 ><span >1.</span><span
 
 <p class=issue >Issue #6: <span
 >&nbsp;&nbsp;&nbsp;&nbsp;
-</span><i>At the current stage, the algorithm hasnt considered any padding,
+</span><i>At the current stage, the algorithm hasn't considered any padding,
 borders or border-spacing. These things will impact the calculation of
 cellMinWidth / cellMaxWidth according to the CSS box model and can be added in
 a future version of this document</i></p>
@@ -747,7 +747,7 @@ <h1 >2<span >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Identify
 
 <p class=MsoListParagraph ><b>2.1.1</b><b><span
 >
-</span>Column Mininum Width (<span >columnMinWidth</span>)</b></p>
+</span>Column Minimum Width (<span >columnMinWidth</span>)</b></p>
 
 <p class=MsoListParagraph ><b>columnMinWidth = max (cellMinWidth </b>of all
 colspan == 1 cells in the column<b>)</b></p>
@@ -827,7 +827,7 @@ <h1 >2<span >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Identify
 preferred width&nbsp;  min width), or (3) each columns minimum width,
 depending on the case. When the algorithm distributes the impact of a
 multi-column cell, the columns minimum and preferred widths are the sole
-contributors to the distributionits specified width is not directly figured
+contributors to the distribution its specified width is not directly figured
 in.&nbsp; This is because the impact of a multi-column cells specified unit
 value width has already been calculated into its columns preferred width. The
 impact of a multi-column cells specified percentage width will be distributed
@@ -848,7 +848,7 @@ <h1 >2<span >&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span>Identify
 
 <p class=issue >Issue #7: <span
 >&nbsp;&nbsp;&nbsp;&nbsp;
-</span><i>&nbsp;&nbsp;As mentioned above, the algorithm hasnt considered any
+</span><i>&nbsp;&nbsp;As mentioned above, the algorithm hasn't considered any
 padding, borders or border-spacing. These inputs will impact the calculation of
 columnMinWidth, columnPreferredWidth and columnSpecifiedWidth according to CSS
 box model, and can be added in future version of this document</i></p>
@@ -925,7 +925,7 @@ <h1 >3.<span >&nbsp;&nbsp;&nbsp;&nbsp; </span>Calculate
 <p  >When the sum
 of preferred percentages exceeds 100%, the algorithm recommends that the
 browser ignore all specified percentages coming after the sum reaches 100% and
-regard them as having 0% specified percent width (though this doesnt
+regard them as having 0% specified percent width (though this doesn't
 necessarily prevent them from being rendered).</p>
 
 <p  >When there
@@ -1204,7 +1204,7 @@ <h1 >5.<span >&nbsp;&nbsp;&nbsp;&nbsp; </span>Distribute
   <p  >columnPreferredWidth</p>
   </td>
   <td width=198 valign=top >
-  <p  >columnPerferredWidth</p>
+  <p  >columnPreferredWidth</p>
   </td>
  </tr>
  <tr>
@@ -1258,7 +1258,7 @@ <h1 >5.<span >&nbsp;&nbsp;&nbsp;&nbsp; </span>Distribute
 of any of the three column types, the algorithm behaves as if the absent
 columns preferred and minimum widths are zero. </p>
 
-<h2>Assigment of values</h2>
+<h2>Assignment of values</h2>
 
 <p  >In order to fulfill Rule No.3, so
 that the sum of the column used widths completely fill the used width of the
@@ -1689,7 +1689,7 @@ <h2>Assigment of values</h2>
   <p  >columnPreferredWidth</p>
   </td>
   <td width=198 valign=top >
-  <p  >columnPerferredWidth</p>
+  <p  >columnPreferredWidth</p>
   </td>
  </tr>
 </table>
@@ -1963,7 +1963,7 @@ <h1 >6.<span >&nbsp;&nbsp;&nbsp;&nbsp; </span>Distribute
 </span>otherwise, equally.</p>
 
 <p class=MsoListParagraph ><span >It
-is only possible when table is all empty. In that case, it doesnt make sense
+is only possible when table is all empty. In that case, it doesn't make sense
 to calculate columnUsedWidth, which should all be 0. </span></p>
 
 <p  >The table's width cannot be
diff --git a/mediaqueries-3/disposition.html b/mediaqueries-3/disposition.html
index 729092f6058..367c5cd55d9 100644
--- a/mediaqueries-3/disposition.html
+++ b/mediaqueries-3/disposition.html
@@ -191,9 +191,9 @@ <h1>Disposition of comments for Media Queries CR</h1>
 precision here ... I'd like to see the following three actions:-
 
 <p>1) A rewording of CSS2.1 Section 4.1.5 to address this point so that it is  
-clear that the error behaviour of the above case is to ignore the entire  
+clear that the error behavior of the above case is to ignore the entire  
 rule, i.e. apply it to no media types. It should also be made clear that  
-this error behaviour applies if a single (apparent) media type is  
+this error behavior applies if a single (apparent) media type is  
 unrecognised [or, indeed, all of several], e.g.
 
 <pre>
@@ -707,7 +707,7 @@ <h1>Disposition of comments for Media Queries CR</h1>
 
 
 	http://lists.w3.org/Archives/Public/www-style/2003Dec/0016
-		NO, just a qutstion
+		NO, just a question
 
 
 
diff --git a/mediaqueries-3/disposition2.html b/mediaqueries-3/disposition2.html
index a2bd2ecb009..4aae8c65bce 100644
--- a/mediaqueries-3/disposition2.html
+++ b/mediaqueries-3/disposition2.html
@@ -337,7 +337,7 @@ <h1>Disposition of comments for Media Queries CR</h1>
 
 
 	http://lists.w3.org/Archives/Public/www-style/2003Dec/0016
-		NO, just a qutstion
+		NO, just a question
 
 
 
diff --git a/mediaqueries-4/Overview.bs b/mediaqueries-4/Overview.bs
index b72d60ff869..d3ce366a6af 100644
--- a/mediaqueries-4/Overview.bs
+++ b/mediaqueries-4/Overview.bs
@@ -1417,7 +1417,7 @@ Block-Axis Overflow: the '@media/overflow-block' feature</h3>
 	except that it honored forced page breaks.
 	Not knowing of any currently-shipping user agent with this type of behavior,
 	the Working Group has decided not to add such a value in this level
-	to avoid miscaracterizing any such user agent.
+	to avoid mischaracterizing any such user agent.
 	Anyone implementing a user agent not adequately described
 	by any of the values specified above
 	is encouraged to contact the Working Group
diff --git a/mediaqueries-4/issues-cr-2017-09-05.html b/mediaqueries-4/issues-cr-2017-09-05.html
index 4c16a32a2ac..777e1a2ac2a 100644
--- a/mediaqueries-4/issues-cr-2017-09-05.html
+++ b/mediaqueries-4/issues-cr-2017-09-05.html
@@ -90,7 +90,7 @@ <h1>Media Queries Level 4 Disposition of Comments for 2017-09-05 CR</h1>
 From:     Christian Biesinger
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4908'>https://github.com/w3c/csswg-drafts/issues/4908</a>
 Closed:   Accepted
-Resolved: Editor's Discression</pre>
+Resolved: Editor's Discretion</pre>
 <pre class='a' id='issue-9'>
 Issue 9. <a href='#issue-9'>#</a>
 Summary:  Consistency of color-gamut keywords
@@ -104,7 +104,7 @@ <h1>Media Queries Level 4 Disposition of Comments for 2017-09-05 CR</h1>
 From:     Andreas Lind
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4534'>https://github.com/w3c/csswg-drafts/issues/4534</a>
 Closed:   Invalid
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 Verified: <a href='https://github.com/w3c/csswg-drafts/issues/4534#issuecomment-557941898'>https://github.com/w3c/csswg-drafts/issues/4534#issuecomment-557941898</a></pre>
 <pre class='a' id='issue-11'>
 Issue 11. <a href='#issue-11'>#</a>
@@ -112,7 +112,7 @@ <h1>Media Queries Level 4 Disposition of Comments for 2017-09-05 CR</h1>
 From:     Yves Lafon
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/4333'>https://github.com/w3c/csswg-drafts/issues/4333</a>
 Closed:   Rejected
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 Verified: <a href='https://github.com/w3c/csswg-drafts/issues/4333#issuecomment-532933242'>https://github.com/w3c/csswg-drafts/issues/4333#issuecomment-532933242</a></pre>
 <pre class='a' id='issue-12'>
 Issue 12. <a href='#issue-12'>#</a>
@@ -175,7 +175,7 @@ <h1>Media Queries Level 4 Disposition of Comments for 2017-09-05 CR</h1>
 From:     Ian Pouncey &amp; Patrick Lauke
 Comment:  <a href='https://github.com/w3c/csswg-drafts/issues/1925'>https://github.com/w3c/csswg-drafts/issues/1925</a>
 Closed:   Accepted
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 Verified: <a href='https://github.com/w3c/csswg-drafts/issues/1925#issuecomment-635290022'>https://github.com/w3c/csswg-drafts/issues/1925#issuecomment-635290022</a></pre>
 <pre class='a' id='issue-21'>
 Issue 21. <a href='#issue-21'>#</a>
@@ -183,7 +183,7 @@ <h1>Media Queries Level 4 Disposition of Comments for 2017-09-05 CR</h1>
 From:     Kivi Shapiro
 Comment:  <a href='https://github.com/w3c/csswg-drafts/pull/4815'>https://github.com/w3c/csswg-drafts/pull/4815</a>
 Closed:   Accepted
-Resolved: Editor's Discression</pre>
+Resolved: Editor's Discretion</pre>
 <pre class='a' id='issue-22'>
 Issue 22. <a href='#issue-22'>#</a>
 Summary:  drop optinal-paged
diff --git a/mediaqueries-4/issues-cr-2017-09-05.txt b/mediaqueries-4/issues-cr-2017-09-05.txt
index 37dbf320b1d..2705b0ff3cc 100644
--- a/mediaqueries-4/issues-cr-2017-09-05.txt
+++ b/mediaqueries-4/issues-cr-2017-09-05.txt
@@ -60,7 +60,7 @@ Summary:  Definition of <ratio> should probably be in css-values
 From:     Christian Biesinger
 Comment:  https://github.com/w3c/csswg-drafts/issues/4908
 Closed:   Accepted
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 ----
 Issue 9.
 Summary:  Consistency of color-gamut keywords
@@ -74,7 +74,7 @@ Summary:  The <general-enclosed> production contains unbalanced parentheses
 From:     Andreas Lind
 Comment:  https://github.com/w3c/csswg-drafts/issues/4534
 Closed:   Invalid
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 Verified: https://github.com/w3c/csswg-drafts/issues/4534#issuecomment-557941898
 ----
 Issue 11.
@@ -82,7 +82,7 @@ Summary:  Use unicode characters for inequality operators
 From:     Yves Lafon
 Comment:  https://github.com/w3c/csswg-drafts/issues/4333
 Closed:   Rejected
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 Verified: https://github.com/w3c/csswg-drafts/issues/4333#issuecomment-532933242
 ----
 Issue 12.
@@ -145,7 +145,7 @@ Summary:  Miscelaneous comments from accessibility Review
 From:     Ian Pouncey & Patrick H. Lauke
 Comment:  https://github.com/w3c/csswg-drafts/issues/1925
 Closed:   Accepted
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 Verified: https://github.com/w3c/csswg-drafts/issues/1925#issuecomment-635290022
 ----
 Issue 21.
@@ -153,7 +153,7 @@ Summary:  Fix typo
 From:     Kivi Shapiro
 Comment:  https://github.com/w3c/csswg-drafts/pull/4815
 Closed:   Accepted
-Resolved: Editor's Discression
+Resolved: Editor's Discretion
 ----
 Issue 22.
 Summary:  drop optinal-paged
diff --git a/mediaqueries-5/Overview.bs b/mediaqueries-5/Overview.bs
index ed61715a84a..f3d5cfb3690 100644
--- a/mediaqueries-5/Overview.bs
+++ b/mediaqueries-5/Overview.bs
@@ -1218,7 +1218,7 @@ Block-Axis Overflow: the '@media/overflow-block' feature</h3>
 	except that it honored forced page breaks.
 	Not knowing of any currently-shipping user agent with this type of behavior,
 	the Working Group has decided not to add such a value in this level
-	to avoid miscaracterizing any such user agent.
+	to avoid mischaracterizing any such user agent.
 	Anyone implementing a user agent not adequately described
 	by any of the values specified above
 	is encouraged to contact the Working Group
diff --git a/resize-observer-1/examples/chat.html b/resize-observer-1/examples/chat.html
index 3c25feafbc6..e4d106b7968 100644
--- a/resize-observer-1/examples/chat.html
+++ b/resize-observer-1/examples/chat.html
@@ -155,7 +155,7 @@ <h4>How to not lose user's scroll position?</h4>
 <p>We can use <code>scroll</code> event to detect when user has scrolled.
 There is no API to distinguish whether scroll event was initiated by user, or
 javascript. This is problematic, because we only want to save user-initated scroll.
-The hacky solution is to use flags to distinguish between user and programatic scroll.
+The hacky solution is to use flags to distinguish between user and programmatic scroll.
 It is implemented as an <a href="#all-demos">Example 2</a>.
 <pre>
 let ro = new ResizeObserver();
@@ -186,7 +186,7 @@ <h4>How to not lose user's scroll position?</h4>
   });
 }
 </pre>
-<p>Example 3 extends Example 2 with smooth scrolling. Unfortunatelly, it has
+<p>Example 3 extends Example 2 with smooth scrolling. Unfortunately, it has
 to implement smooth scrolling from scratch, instead of using
 <code>scrollIntoView(behavior:'smooth')</code>. scrollIntoView fires scroll
 events that cannot be distinguished from user initiated events.</p>
diff --git a/resize-observer-1/explainer.md b/resize-observer-1/explainer.md
index 883390d5c4e..32133a3f63f 100644
--- a/resize-observer-1/explainer.md
+++ b/resize-observer-1/explainer.md
@@ -10,10 +10,10 @@ Javascript DOM manipulation stays in sync with viewport size by listening to `wi
 
 Responsive Web Apps can be built with components.
 These components need to be responsive too.
-Unfortunatelly, Web Platform currently does not provide a way for components to keep track of their size.
+Unfortunately, Web Platform currently does not provide a way for components to keep track of their size.
 
 There is no component counterpart to CSS media queries.
-Attempts to design such were unsucessful due to their [inability to deal](http://www.xanthir.com/b4PR0) with circular references.
+Attempts to design such were unsuccessful due to their [inability to deal](http://www.xanthir.com/b4PR0) with circular references.
 
 There is no component counterpart to `window.resize` event either.
 ResizeObserver wants to be that counterpart.
diff --git a/scroll-animations-1/EXPLAINER.md b/scroll-animations-1/EXPLAINER.md
index 6e88c767b3a..7fdeb9d13d6 100644
--- a/scroll-animations-1/EXPLAINER.md
+++ b/scroll-animations-1/EXPLAINER.md
@@ -53,7 +53,7 @@ inspected, controlled via a common animations API.
 These are a class of animation whose progress is driven by time but whose activation may be
 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
+same way that scroll-linked animations do. This is because only their activation is tied to scroll
 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
@@ -61,7 +61,7 @@ would want to do it for a CSS transition (as opposed to a CSS animation). Unfort
 possible to trigger CSS transitions from the compositor thread (because triggering a transition
 requires style resolution, which cannot be performed on the compositor thread).
 
-Earlier versions of this specification included a triggering mechanims. But given the extent to
+Earlier versions of this specification included a triggering mechanism. But given the extent to
 which triggering complicated the API and because of the smaller benefit that these type of
 animation will receive, we decided it wasn't worth it if you can't use it for transitions, so this
 feature was remove and scroll-triggered animations are non-goal for this API.
diff --git a/scroll-animations-1/Use cases.md b/scroll-animations-1/Use cases.md
index eaed34befa5..42d213e596a 100644
--- a/scroll-animations-1/Use cases.md	
+++ b/scroll-animations-1/Use cases.md	
@@ -37,7 +37,7 @@ Scroll position controls progress:
 # Deferred Usecases
 
 See [EXPLAINER](https://github.com/w3c/csswg-drafts/blob/master/scroll-animations-1/EXPLAINER.md#non-goals)
-for an explanation of why theses usecases are deferreing in the first version of this specification.
+for an explanation of why theses usecases are deferring in the first version of this specification.
 The design space for triggering animations is still open. We welcome input on this subject for next
 revision of this specification.
 
diff --git a/selectors-3/Overview.html b/selectors-3/Overview.html
index 051b0088605..fa4d39e2075 100644
--- a/selectors-3/Overview.html
+++ b/selectors-3/Overview.html
@@ -2535,7 +2535,7 @@ <h4 id=first-formatted-line><span class=secno>7.1.1. </span>First formatted
    the first line only inherits properties applicable to the <a
    href="#sel-first-line"><code>::first-line</code></a> pseudo-element from
    the <a href="#sel-first-line"><code>::first-line</code></a>
-   pseudo-element. For all other properties inheritence is from the
+   pseudo-element. For all other properties inheritance is from the
    non-pseudo-element parent of the first line pseudo element. (The portion
    of a child element that does not occur on the first line always inherits
    from the parent of that child.)
diff --git a/selectors-3/Overview.src.html b/selectors-3/Overview.src.html
index 47e448edb68..6cc61c3f179 100644
--- a/selectors-3/Overview.src.html
+++ b/selectors-3/Overview.src.html
@@ -955,7 +955,7 @@ <h4 id=def-values>Default attribute values in DTDs</h4>
 1.0.)</p>
 
 <p class="note"><strong>Note:</strong> Typically, implementations
-choose to ignore external subsets. This corresponds to the behaviour
+choose to ignore external subsets. This corresponds to the behavior
 of non-validating processors as defined by the XML specification.</p>
 
 <div class="example">
@@ -1954,7 +1954,7 @@ <h4 id="first-formatted-line">First formatted line definition in CSS</h4>
 <p>During CSS inheritance, the portion of a child element that occurs
 on the first line only inherits properties applicable to the
 <code>::first-line</code> pseudo-element from the <code>::first-line</code>
-pseudo-element. For all other properties inheritence is from the
+pseudo-element. For all other properties inheritance is from the
 non-pseudo-element parent of the first line pseudo element. (The portion
 of a child element that does not occur on the first line always inherits
 from the parent of that child.)
diff --git a/selectors-4/Overview.bs b/selectors-4/Overview.bs
index 267af75a12e..898f916273a 100644
--- a/selectors-4/Overview.bs
+++ b/selectors-4/Overview.bs
@@ -254,7 +254,7 @@ Selectors Overview</h2>
 			<tr>
 				<td><code>E:local-link</code>
 				<td>an E element being the source anchor of a hyperlink
-					targetting the current URL
+					targeting the current URL
 				<td>[[#the-local-link-pseudo]]
 				<td>4
 			<tr>
@@ -2052,7 +2052,7 @@ The Local Link Pseudo-class: '':local-link''</h3>
 	is not taken into account in the comparison.
 
 	<div class="example">
-		For example, the following rule prevents links targetting the
+		For example, the following rule prevents links targeting the
 		current page from being underlined when they are part of the
 		navigation list:
 
@@ -2060,7 +2060,7 @@ The Local Link Pseudo-class: '':local-link''</h3>
 	</div>
 
 	Note: The current URL of a page can change as a result of user actions
-	such as activating a link targetting a different fragment within the same page;
+	such as activating a link targeting a different fragment within the same page;
 	or by use of the <code>pushState</code> API;
 	as well as by the more obvious actions of navigating to a different page
 	or following a redirect (which could be initiated by protocols such as HTTP,
@@ -2527,7 +2527,7 @@ The Selected-option Pseudo-class: '':checked''</h4>
 <h4 id="indeterminate">
 The Indeterminate-value Pseudo-class: '':indeterminate''</h4>
 
-	The <dfn id='indetermine-pseudo'>:indeterminate</dfn> pseudo-class applies to UI elements whose
+	The <dfn id='indeterminate-pseudo'>:indeterminate</dfn> pseudo-class applies to UI elements whose
 	value is in an indeterminate state.
 	For example, radio and checkbox elements can be toggled between checked and unchecked states,
 	but are sometimes in an indeterminate state, neither checked nor unchecked.
diff --git a/selectors-4/deferred-for-level-5 b/selectors-4/deferred-for-level-5
index 2b964db8185..fc867c53f6e 100644
--- a/selectors-4/deferred-for-level-5
+++ b/selectors-4/deferred-for-level-5
@@ -44,7 +44,7 @@ The local link pseudo-class '':local-link''</h3>
 	otherwise all portions of the URL are considered.
 
 	<div class="example">
-		For example, the following rule prevents links targetting the
+		For example, the following rule prevents links targeting the
 		current page from being underlined when they are part of the
 		navigation list:
 
diff --git a/shared/transition-templates/cr-updated.md b/shared/transition-templates/cr-updated.md
index 55235819b3a..fc95872d38e 100644
--- a/shared/transition-templates/cr-updated.md
+++ b/shared/transition-templates/cr-updated.md
@@ -8,7 +8,7 @@ FULL TITLE
 
 https://drafts.csswg.org/DIRECTORY/
 
-First Tuesday or Thursday after a sucessful transition decision.
+First Tuesday or Thursday after a successful transition decision.
 
 ## The document Abstract and Status sections
 
diff --git a/shared/transition-templates/pr.md b/shared/transition-templates/pr.md
index 35621744076..facec436d7c 100644
--- a/shared/transition-templates/pr.md
+++ b/shared/transition-templates/pr.md
@@ -9,7 +9,7 @@ FULL TITLE
 
 https://drafts.csswg.org/DIRECTORY/
 
-First Tuesday or Thursday after a sucessful transition decision.
+First Tuesday or Thursday after a successful transition decision.
 
 ## The document Abstract and Status sections
 
diff --git a/web-animations-1/Overview.bs b/web-animations-1/Overview.bs
index ecf0eb9711a..5c9ab00818e 100644
--- a/web-animations-1/Overview.bs
+++ b/web-animations-1/Overview.bs
@@ -2302,7 +2302,7 @@ These states are only established for the duration of a single
 [=animation frame=] and are primarily a convenience for describing stative parts
 of the model.
 
-These states and their useage within the model are summarized as
+These states and their usage within the model are summarized as
 follows:
 
 :   <a>in play</a>
@@ -3142,7 +3142,7 @@ in each property's property definition table:
     that are <a>not animatable</a> will still exhibit
     the usual behavior for an <a>animation effect</a>
     such as firing events and
-    delaying the fulfilment of the <a>animation</a>'s
+    delaying the fulfillment of the <a>animation</a>'s
     <a>current finished promise</a>.
 
   <dt><dfn>discrete</dfn>
@@ -4298,7 +4298,7 @@ interface Animation : EventTarget {
       recalculating em units based on changes to the computed ''font-size''
       in the way the values produced by a live animation would.
 
-      In order to retain full fidelty of a filling animation's result after it
+      In order to retain full fidelity of a filling animation's result after it
       has been replaced (see [[#replacing-animations]]),
       the {{Animation/persist()}} method may be used,
       but note that doing so will mean the animation continues to consume
@@ -4449,7 +4449,7 @@ apart from the timing model.
 :   <dfn method for=AnimationEffect>getTiming()</dfn>
 ::  Returns the specified timing properties for this <a>animation effect</a>.
 
-    For the correspondance between the members of the returned {{EffectTiming}}
+    For the correspondence between the members of the returned {{EffectTiming}}
     object and properties of the [[#timing-model|timing model]], see the
     the {{EffectTiming}} interface.
 
@@ -4642,7 +4642,7 @@ dictionary OptionalEffectTiming {
     however, return <code>auto</code> for the {{EffectTiming/duration}} member
     returned from {{AnimationEffect/getTiming()}}.
 
-    This is a forwards-compatiblity measure since a future level of this
+    This is a forwards-compatibility measure since a future level of this
     specification is expected to introduce group effects where the
     <code>auto</code> value expands to include the duration of the child
     effects.
diff --git a/web-animations-2/Overview.bs b/web-animations-2/Overview.bs
index 9d092abed94..2fe00d30950 100644
--- a/web-animations-2/Overview.bs
+++ b/web-animations-2/Overview.bs
@@ -429,7 +429,7 @@ as CSS Animations [[CSS-ANIMATIONS-1]].
 1.  If |reset current time on resume| is set:
 
     * Set <var>previous current time</var> to unresolved.
-    * Set the |reset curent time on resume| flag to false.
+    * Set the |reset current time on resume| flag to false.
 
 1.  Perform the steps corresponding to the <em>first</em> matching
     condition from the following, if any:
@@ -616,7 +616,7 @@ updating [=custom effects=].
 <h4 id='pausing-an-animation-section'>Pausing an animation</h4>
 
 The procedure to [=pause an animation=] needs to refer to not on the [=target
-effect=] but also any descedants of the [=target effect=].
+effect=] but also any descendants of the [=target effect=].
 
 Likewise, the procedure to [=pause an animation=] needs to include scheduling
 a task for updating [=custom effects=].
@@ -681,7 +681,7 @@ This specification defines two types of <a>animation effects</a>:
 
 <h4 id="the-active-interval">The active interval</h4>
 
-In this level of the specification the lower bound of the acive interval is
+In this level of the specification the lower bound of the active interval is
 defined as:
 
 >     The lower bound of the <a>active interval</a> is determined by the
@@ -1653,7 +1653,7 @@ Update the description of an effect that targets a non-animated property as:
 >     <a>not animatable</a> will still exhibit the
 >     usual behavior for an <a>animation effect</a> such as
 >     occupying time in a <a>sequence effect</a> and
->     delaying the fulfilment of an <a>animation</a>'s <a>current finished
+>     delaying the fulfillment of an <a>animation</a>'s <a>current finished
 >     promise</a>.
 
 <h3 id="keyframe-effects">Keyframe Effects</h3>
@@ -1688,7 +1688,7 @@ after the step to apply the keyframe effect composite mode.
               the animation type of the target property does not define a
               procedure for accumulation or addition, the default definition
               for these procedures result in <var>V</var><sub>b</sub> being
-              returned. When performing iteration composition on propreties
+              returned. When performing iteration composition on properties
               that do not support accumulation, the result should be the
               initial property value of <var>target property</var> on
               <var>keyframe</var>, hence we make this
@@ -1836,7 +1836,7 @@ In many cases this can be achieved by inserting a custom effect with
 a step-start easing that spans the period during which the action
 should be triggered.
 However, this can impose additional layout requirements on the
-content which might be cumbersome to accomodate.
+content which might be cumbersome to accommodate.
 
 Some alternatives under consideration:
 
@@ -2309,7 +2309,7 @@ a {{EffectTiming}} object.</p>
 The <dfn lt="next sibling not included">next sibling of
 <var>effect</var> not included</dfn> in a set of <a>animation
 effects</a>, <var>effects</var> is determined using the following
-teps:</p>
+steps:</p>
 
 1.  Let <var>context effect</var> be <var>effect</var>.
 2.  While the <a>next sibling</a> of <var>context effect</var> is not
diff --git a/web-animations-2/img/time-calculations.svg b/web-animations-2/img/time-calculations.svg
index 6a36802b18a..d239fa77a35 100644
--- a/web-animations-2/img/time-calculations.svg
+++ b/web-animations-2/img/time-calculations.svg
@@ -200,7 +200,7 @@
       </g>
     </g>
   </g>
-  <!-- Overal progress -->
+  <!-- Overall progress -->
   <g transform="translate(0 500)">
     <text class="stepLabel">
       &#x2462; Calculate the overall progress