[meta] Consistent spelling of lowercase/uppercase

Author: fantasai

css-color-4/Overview.bs

@@ -5878,7 +5878,7 @@ and there shall be no thousands separator.
 
 For syntactic forms which support [=missing color components=],
 the value ''none'' (equivalently NONE, nOnE, etc),
-shall be serialized in all-lower case
+shall be serialized in all-lowercase
 as the string "none".
 
 

css-counter-styles-3/Overview.bs

@@ -180,7 +180,7 @@ Defining Custom Counter Styles: the ''@counter-style'' rule</h2>
 	and so won't be usable there.
 
 	Counter style names are case-sensitive.
-	However, the names defined in this specification are ASCII lower-cased on parse
+	However, the names defined in this specification are ASCII lowercased on parse
 	wherever they are used as counter styles, e.g.
 	in the 'list-style' set of properties,
 	in the ''@counter-style'' rule,

css-print/Overview.bs

@@ -1134,9 +1134,9 @@ HR              { border: 1px inset }
 </div>
 </li>
 
-<li>The lower case letters of the content of the <code>abbr</code> and <code>acronym</code> elements should be rendered as scaled capital
+<li>The lowercase letters of the content of the <code>abbr</code> and <code>acronym</code> elements should be rendered as scaled capital
 letters, at approximately 75% of their size at the current font size. Upper case letters will be unchanged. Printers may 
-also choose to simply render lower case letters as upper case letters without scaling.
+also choose to simply render lowercase letters as uppercase letters without scaling.
 
 <div class="editorial">
 <!-- Editorial Annotation -->

css-values-3/Overview.bs

@@ -1341,7 +1341,7 @@ Absolute Lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	was made because too much existing content relies on the assumption of 96dpi,
 	and breaking that assumption broke the content.)
 
-	Note: Units are [=ASCII case-insensitive=] and serialize as lower case, for example 1Q serializes as 1q.
+	Note: Units are [=ASCII case-insensitive=] and serialize as lowercase, for example 1Q serializes as 1q.
 
 	<wpt>
 	css/css-values/absolute-length-units-001.html
@@ -1551,7 +1551,7 @@ Frequency Units: the <<frequency>> type and ''Hz'', ''kHz'' units</h3>
 	All <<frequency>> units are <a>compatible</a>,
 	and ''hz'' is their <a>canonical unit</a>.
 
-	Note: Units are [=ASCII case-insensitive=] and serialize as lower case, for example 1Hz serializes as 1hz.
+	Note: Units are [=ASCII case-insensitive=] and serialize as lowercase, for example 1Hz serializes as 1hz.
 
 <!--
 ████████  ████████  ██████   ███████

css-values-4/Overview.bs

@@ -2449,7 +2449,7 @@ Absolute Lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	was made because too much existing content relies on the assumption of 96dpi,
 	and breaking that assumption broke the content.)
 
-	Note: Units are [=ASCII case-insensitive=] and serialize as lower case, for example 1Q serializes as 1q.
+	Note: Units are [=ASCII case-insensitive=] and serialize as lowercase, for example 1Q serializes as 1q.
 
 	<wpt>
 	css/css-values/absolute-length-units-001.html
@@ -2659,7 +2659,7 @@ Frequency Units: the <<frequency>> type and ''Hz'', ''kHz'' units</h3>
 	All <<frequency>> units are <a>compatible</a>,
 	and ''hz'' is their <a>canonical unit</a>.
 
-	Note: Units are [=ASCII case-insensitive=] and serialize as lower case, for example 1Hz serializes as 1hz.
+	Note: Units are [=ASCII case-insensitive=] and serialize as lowercase, for example 1Hz serializes as 1hz.
 
 <!--
 ████████  ████████  ██████   ███████

css-variables-1/Overview.bs

@@ -1236,7 +1236,7 @@ APIs</h2>
 	</wpt>
 
 	Note: Custom properties do not appear on a CSSStyleDeclaration object in camel-cased form,
-	because their names may have both upper and lower case letters
+	because their names may have both upper and lowercase letters
 	which indicate distinct custom properties.
 	The sort of text transformation that automatic camel-casing performs is incompatible with this.
 	They can still be accessed by their proper name via <a method>getPropertyValue()</a>/etc.

css-variables-2/Overview.bs

@@ -1340,7 +1340,7 @@ APIs</h2>
 	</wpt>
 
 	Note: Custom properties do not appear on a CSSStyleDeclaration object in camel-cased form,
-	because their names may have both upper and lower case letters
+	because their names may have both upper and lowercase letters
 	which indicate distinct custom properties.
 	The sort of text transformation that automatic camel-casing performs is incompatible with this.
 	They can still be accessed by their proper name via <a method>getPropertyValue()</a>/etc.

css2/Overview.bs

@@ -12333,7 +12333,7 @@ Otherwise the values must be matched exactly or font-style will fail.
 <li>'font-variant' is tried next. ''small-caps'' matches (1) a
 font labeled as ''small-caps'', (2) a font in which the small caps are
 synthesized, or (3) a font where all lowercase letters are replaced by
-upper case letters. A small-caps font may be synthesized by
+uppercase letters. A small-caps font may be synthesized by
 electronically scaling uppercase letters from a normal font.
 ''font-variant/normal'' matches a font's normal (non-small-caps) variant. A font cannot fail to have a normal variant. A font
  that is only available as small-caps shall be selectable as either a ''font-variant/normal'' face or a ''small-caps'' face.
@@ -12663,14 +12663,14 @@ Computed Value: as specified
 
 
 <p>Another type of variation within a font family is the small-caps.
-In a small-caps font the lower case letters look similar to the
+In a small-caps font the lowercase letters look similar to the
 uppercase ones, but in a smaller size and with slightly different
 proportions. The 'font-variant' property selects that font.
 </p>
 <p>A value of <dfn class="css" data-dfn-for="font-variant" data-dfn-type="value" id="valdef-font-variant-normal">normal</dfn> selects a font that is not a small-caps font,
 <dfn class="css" data-dfn-for="font-style" data-dfn-type="value" id="valdef-font-style-small-caps">small-caps</dfn> selects a small-caps font. It is acceptable (but not
 required) in CSS&nbsp;2 if the small-caps font is a created by taking a
-normal font and replacing the lower case letters by scaled uppercase
+normal font and replacing the lowercase letters by scaled uppercase
 characters. As a last resort, uppercase letters will be used as
 replacement for a small-caps font.
 </p>