[css-values] Fix editorial nits reported by timeless (issues-cr-2015#4) <https://lists.w3.org/Archives/Public/www-style/2015Jul/0050.html>

Author: fantasai

css-values/Overview.bs

@@ -116,7 +116,7 @@ Component value types</h3>
 	such as “+”,
 	must be written enclosed in single quotes.
 
-	<dfn lt="," id='comb-comma' export grammar>Commas</dfn> specified in the grammar are <strong>implicitly omittable</strong> in some circumstances,
+	<strong><dfn lt="," id='comb-comma' export grammar>Commas</dfn> specified in the grammar are implicitly omissible</strong> in some circumstances,
 	when used to separate optional terms in the grammar.
 	Within a top-level list in a property or other CSS value,
 	or a function's argument list,
@@ -130,7 +130,7 @@ Component value types</h3>
 			all items following the comma have been omitted
 
 		<li>
-			multiple commas would be adjacent (ignoring whitespace/comments),
+			multiple commas would be adjacent (ignoring <a href="https://www.w3.org/TR/css-syntax/#whitespace">white space</a>/comments),
 			due to the items between the commas being omitted.
 	</ul>
 
@@ -196,7 +196,7 @@ Component value combinators</h3>
 	[ a b ] | [ c || [ d && [ e f ]]]
 	</pre>
 
-	For re-orderable combinators (||, &&),
+	For reorderable combinators (||, &&),
 	ordering of the grammar does not matter:
 	components in the same grouping may be interleaved in any order.
 	Thus, the following lines are equivalent:
@@ -234,7 +234,7 @@ Component value multipliers</h3>
 
 		<li>A hash mark (<dfn id='mult-comma'>#</dfn>) indicates that the preceding type, word, or
 			group occurs one or more times, separated by comma tokens
-			(which may optionally be surrounded by white space and/or comments).
+			(which may optionally be surrounded by <a href="https://www.w3.org/TR/css-syntax/#whitespace">white space</a> and/or comments).
 			It may optionally be followed by the curly brace forms, above,
 			to indicate precisely how many times the repetition occurs,
 			like ''&lt;length>#{1,4}''.
@@ -291,7 +291,7 @@ Combinator and Multiplier Patterns</h3>
 Component values and white space</h3>
 
 	Unless otherwise specified,
-	white space and/or comments may appear before, after, and/or between
+	<a href="https://www.w3.org/TR/css-syntax/#whitespace">white space</a> and/or comments may appear before, after, and/or between
 	components combined using the above
 	<a href="#component-combinators">combinators</a> and
 	<a href="#component-multipliers">multipliers</a>.
@@ -302,7 +302,7 @@ Component values and white space</h3>
 	with the number ''1'' and the identifier ''em2em'',
 	which is an invalid unit.
 	In this case, a space would be required before the ''2''
-	to get this parsed as the two lengths ''1em''and ''2em''.
+	to get this parsed as the two lengths ''1em'' and ''2em''.
 
 <h3 id="value-examples">
 Property value examples</h3>
@@ -351,7 +351,7 @@ Textual Data Types</h2>
 
 	An <dfn>identifier</dfn> is a sequence of characters conforming to the <<ident-token>> grammar. [[!CSS3SYN]]
 	Identifiers cannot be quoted;
-	otherwise they would be interpreted as a string.
+	otherwise they would be interpreted as strings.
 
 <!--
 ██    ██ ████████ ██    ██ ██      ██  ███████  ████████  ████████   ██████
@@ -370,7 +370,7 @@ Pre-defined Keywords</h3>
 	keywords with a pre-defined meaning appear literally.
 	Keywords are CSS <a>identifiers</a>
 	and are interpreted <a lt="ASCII case-insensitive">ASCII case-insensitively</a>
-	(i.e., \[a-z] and \[A-Z] are equivalent).
+	(i.e., [a-z] and \[A-Z] are equivalent).
 
 	<div class="example">
 		For example, here is the value definition for the 'border-collapse'
@@ -526,8 +526,9 @@ Resource Locators: the <<url>> type</h3>
 	Because these alternate ways of writing a <<url>> are not <a>functional notations</a>,
 	they cannot accept any <<url-modifier>>s.
 
-	Note: The special parsing rules for the legacy quotation mark-less <<url>> syntax
-	means that parentheses, whitespace characters, single quotes (&#39;) and double quotes (") appearing in a URL
+	Note: The special parsing rules for the legacy quotation-mark&ndash;less <<url>> syntax
+	means that parentheses, <a href="https://www.w3.org/TR/css-syntax/#whitespace">whitespace</a> characters,
+	single quotes (&#39;) and double quotes (") appearing in a URL
 	must be escaped with a backslash,
 	e.g. ''url(open\(parens)'', ''url(close\)parens)''.
 	Depending on the type of URL,
@@ -781,7 +782,7 @@ Relative lengths</h3>
 		<tr><td>''vw''
 		    <td>1% of viewport's width
 		<tr><td>''vh''
-		    <td>1% viewport's height
+		    <td>1% of viewport's height
 		<tr><td>''vmin''
 		    <td>1% of viewport's smaller dimension
 		<tr><td>''vmax''
@@ -834,7 +835,7 @@ Font-relative lengths: the ''em'', ''ex'', ''ch'', ''rem'' units</h4>
 
 		<dt><dfn lt="ex">ex unit</dfn>
 		<dd>
-			Equal to the used x-height of the <a href="https://www.w3.org/TR/css3-fonts/#first-available-font">first available font</a>. [[!CSS3-FONTS]]
+			Equal to the used x-height of the <a href="https://www.w3.org/TR/css3-fonts/#first-available-font">first available font</a> [[!CSS3-FONTS]].
 			The x-height is so called because it is often equal to the height of the lowercase "x".
 			However, an ''ex'' is defined even for fonts that do not contain an "x".
 			The x-height of a font can be found in different ways. Some fonts
@@ -985,19 +986,19 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	For such devices it is recommended that the pixel unit
 	refer to the whole number of device pixels that best approximates the reference pixel.
 
-	Note: Note that if the anchor unit is the pixel unit,
+	Note: If the anchor unit is the pixel unit,
 	the physical units might not match their physical measurements.
 	Alternatively if the anchor unit is a physical unit,
 	the pixel unit might not map to a whole number of device pixels.
 
-	Note: Note that this definition of the pixel unit and the physical units
+	Note: This definition of the pixel unit and the physical units
 	differs from previous versions of CSS.
 	In particular, in previous versions of CSS the pixel unit and the physical units
 	were not related by a fixed ratio:
 	the physical units were always tied to their physical measurements
 	while the pixel unit would vary to most closely match the reference pixel.
 	(This change was made because too much existing content relies on the assumption of 96dpi,
-	and breaking that assumption breaks the content.)
+	and breaking that assumption broke the content.)
 
 	The <dfn export>reference pixel</dfn> is the visual angle of one pixel on a device with a pixel density of 96dpi
 	and a distance from the reader of an arm's length.
@@ -1043,7 +1044,9 @@ Absolute lengths: the ''cm'', ''mm'', ''q'', ''in'', ''pt'', ''pc'', ''px'' unit
 		             square reference pixel is implemented by 16 dots. For
 		             the monitor screen, one square reference pixel is
 		             implemented by a single dot.'>
-		<figcaption>Showing that more device pixels (dots) are needed to cover a 1px by 1px area on a high-resolution device than on a low-res one</figcaption>
+		<figcaption>Showing that more device pixels (dots) are needed to cover a 1px by 1px area
+		on a high-resolution device than on a lower-resolution one
+		(of the same approximate viewing distance)</figcaption>
 	</figure>
 
 <h2 id="other-units">
@@ -1170,21 +1173,21 @@ Resolution Units: the <<resolution>> type and ''dpi'', ''dpcm'', ''dppx'' units<
 
 	<dl export>
 		<dt><dfn>dpi</dfn>
-		<dd>dots per inch
+		<dd>Dots per inch.
 
 		<dt><dfn>dpcm</dfn>
-		<dd>dots per centimeter
+		<dd>Dots per centimeter.
 
 		<dt><dfn>dppx</dfn>
-		<dd>dots per ''px'' unit
+		<dd>Dots per ''px'' unit.
 	</dl>
 
 	The <<resolution>> unit represents the size of a single "dot" in a graphical representation
 	by indicating how many of these dots fit in a CSS ''in'', ''cm'', or ''px''.
 	For uses, see e.g. the  ''resolution'' media query in [[MEDIAQ]]
 	or the 'image-resolution' property defined in [[CSS3-IMAGES]].
 
-	Note: Note that due to the 1:96 fixed ratio of CSS ''in'' to CSS ''px'',
+	Note: Due to the 1:96 fixed ratio of CSS ''in'' to CSS ''px'',
 	''1dppx'' is equivalent to ''96dpi''.
 	This corresponds to the default resolution of images displayed in CSS: see 'image-resolution'.
 
@@ -1261,15 +1264,16 @@ Functional Notations</h2>
 	(i.e. a <<function-token>>)
 	followed by the argument(s) to the notation
 	followed by a right parenthesis.
-	White space is allowed, but optional, immediately inside the parentheses.
+	<a href="https://www.w3.org/TR/css-syntax/#whitespace">White space</a> is allowed, but optional,
+	immediately inside the parentheses.
 	Functions can take multiple arguments,
 	which are formatted similarly to a CSS property value.
 
 	Some legacy functional notations, such as ''rgba()'', use commas unnecessarily,
 	but generally commas are only used to separate items in a list,
 	or pieces of a grammar that would be ambiguous otherwise.
 	If a comma is used to separate arguments,
-	whitespace is optional before and after the comma.
+	<a href="https://www.w3.org/TR/css-syntax/#whitespace">white space</a> is optional before and after the comma.
 
 	<div class="example">
 		<pre>
@@ -1383,8 +1387,9 @@ Syntax</h4>
 
 	<p noexport>Where a <dfn>&lt;dimension></dfn> is a <a>dimension</a>.
 
-	In addition, whitespace is required on both sides of the ''+'' and ''-'' operators.
-	(The ''*'' and ''/'' operaters can be used without whitespace around them.)
+	In addition, <a href="https://www.w3.org/TR/css-syntax/#whitespace">white space</a>
+	is required on both sides of the ''+'' and ''-'' operators.
+	(The ''*'' and ''/'' operaters can be used without white space around them.)
 
 	UAs must support ''calc()'' expressions of at least 20 terms,
 	where each <code>NUMBER</code>, <code>DIMENSION</code>, or <code>PERCENTAGE</code> is a term.
@@ -1455,8 +1460,8 @@ Type Checking</h4>
 	(as purely-numeric expressions can be evaluated without any additional
 	information at parse time).
 
-	Note: Note that algebraic simplifications do not affect the validity of the ''calc()'' expression or its resolved type.
-	For example, ''calc(5px - 5px + 10s)'' or ''calc(0 * 5px + 10s)'' are both invalid
+	Note: Algebraic simplifications do not affect the validity of the ''calc()'' expression or its resolved type.
+	For example, ''calc(5px - 5px + 10s)'' and ''calc(0 * 5px + 10s)'' are both invalid
 	due to the attempt to add a length and a time.
 
 <h4 id='calc-computed-value'>
@@ -1518,7 +1523,7 @@ Range Checking</h4>
 	The value resulting from an expression must be clamped to the
 	range allowed in the target context.
 
-	Note: Note this requires all contexts accepting ''calc()''
+	Note: This requires all contexts accepting ''calc()''
 	to define their allowable values as a closed (not open) interval.
 
 	<div class=example>
@@ -1649,12 +1654,12 @@ Toggling Between Values: ''toggle()''</h3>
 	or there was no match,
 	the computed value of ''toggle()'' is the computed value that the first argument represents.
 
-	Note: Note that ''toggle()'' explicitly looks at the computed value of the parent,
+	Note: That ''toggle()'' explicitly looks at the computed value of the parent,
 	so it works even on non-inherited properties.
 	This is similar to the ''inherit'' keyword,
 	which works even on non-inherited properties.
 
-	Note: Note that the <a href="https://www.w3.org/TR/CSS21/cascade.html#computed-value">computed value</a> of a property is an abstract set of values,
+	Note: That the <a href="https://www.w3.org/TR/CSS21/cascade.html#computed-value">computed value</a> of a property is an abstract set of values,
 	not a particular serialization [[!CSS21]],
 	so comparison between computed values should always be unambiguous and have the expected result.
 	For example,
@@ -1685,7 +1690,7 @@ Toggling Between Values: ''toggle()''</h3>
 		</pre>
 
 		Note that, since ''1px'' appears twice in the top and bottom margins,
-		they will cycle between only two value
+		they will cycle between only two values
 		while the left and right margins cycle through three.
 		In other words, the declarations above will yield the same computed values
 		as the longhand declarations below:
@@ -1750,7 +1755,7 @@ Ian's proposal:
 	If it's absent,
 	the default value for the given <<type-or-unit>> (from the list below) is implied.
 
-	Note: Note that, unlike <<toggle-value>>s,
+	Note: Unlike <<toggle-value>>s,
 	an ''attr()'' <<attr-fallback>> value may contain top-level commas,
 	as it is always the last argument in the functional notation.
 
@@ -1761,7 +1766,7 @@ Ian's proposal:
 			the attr() expression's type is valid where the attr() expression is placed,
 
 		<li>
-			if the attribute name is given with a namespace prefix, the prefix is defined
+			the namespace prefix of the attribute name, if any, is defined,
 
 		<li>
 			the <<attr-fallback>> is valid where the attr() expression is placed,
@@ -1782,7 +1787,7 @@ Ian's proposal:
 		like in ''width: attr(size px, auto);''.
 
 		If the attr() is used alongside other values to form the full property value,
-		however, the default value must match the attr()&#39;s type.
+		however, then the default value must match the attr()&#39;s type.
 		For example, ''box-shadow: attr(size px, inset) 5px 10px blue;'' is invalid,
 		even though it would create a valid declaration if you substituted the attr() expression
 		with either a ''px'' length <em>or</em> the ''box-shadow/inset'' keyword.
@@ -1791,7 +1796,8 @@ Ian's proposal:
 	If the specified attribute exists on the element,
 	the value of the attribute must be parsed as required by the <<type-or-unit>> argument
 	(as defined in the list below).
-	Unless the type is ''string'', it must first be stripped of leading and trailing white space.
+	Unless the type is ''string'', it must first be stripped of leading and trailing
+	<a href="https://www.w3.org/TR/css-syntax/#whitespace">white space</a>.
 	The resulting value is the attr() expression's value.
 	If the value did not parse as required,
 	the attr() expression's value is its fallback value.
@@ -1804,9 +1810,9 @@ Ian's proposal:
 			The attribute value is taken as the contents of a CSS <<string>>.
 			The default is the empty string.
 
-			Note: this does not reparse the attribute value with the CSS parser.
-			So, for example, an attribute whose value is "\33" will produce a string containing those three characters,
-			not a string containing "3" (the character that the escape would evaluate to).
+			Note: This does not reparse the attribute value with the CSS parser.
+			So, for example, an attribute whose value is "\51" will produce a string containing those three characters,
+			not a string containing "Q" (the character that the escape would evaluate to).
 
 		<dt>''color''
 		<dd>
@@ -2098,7 +2104,7 @@ Changes</h2>
 		<li>Added notation for restricting the length of comma-separated lists
 			specified with the ''#'' notation.
 		<li>Clarified handling of ''toggle()'' when used in shorthand declarations.
-		<li>Clarified that stringing together re-orderable combinations allows interleaving.
+		<li>Clarified that stringing together reorderable combinations allows interleaving.
 		<li>Changed syntax references from the 2.1 grammar to the Syntax spec.
 	</ul>