[css-values-3][editorial] Fixed Bikeshed issues

Author: SebastianZ

css-values-3/Overview.bs

@@ -18,16 +18,20 @@ Ignored Vars: Cn+1, n
 Inline Github Issues: no
 Default Highlight: css
 WPT Display: open
+Ignore MDN Failure: calc-constants, exponent-funcs, funcdef-mod, funcdef-rem, funcdef-round, sign-funcs, trig-funcs
 </pre>
 <pre class='link-defaults'>
-spec: css-backgrounds-3; type: type; text: <position>
-spec: css-backgrounds-3; type: property; text: border-color
-spec: css-backgrounds-3; type: property; text: box-shadow
-spec: css2; type: property; text: border-collapse
+spec: css-backgrounds-3;
+	type: property;
+		text: border-color
+		text: box-shadow
+	type: type; text: <position>
 spec: css-color-4; type: value; text: currentcolor
+spec: css2; type: property; text: border-collapse
 spec: infra; type: dfn; text: string
 </pre>
 <pre class="ignored-specs">
+spec: css-borders-4;
 spec: css-device-adapt-1;
 </pre>
 
@@ -819,15 +823,15 @@ Range Restrictions and Range Definition Notation</h3>
 	however in reality implementations have finite capacity.
 	[=UAs=] should support reasonably useful ranges and precisions.
 	Range extremes that are ideally unlimited
-	are indicated using &infin; or &minus;&infin; as appropriate.
-	For example, <<length [0, &infin;]>> indicates a non-negative length.
+	are indicated using ∞ or &minus;∞ as appropriate.
+	For example, <<length [0, ∞]>> indicates a non-negative length.
 
 	If no range is indicated,
 	either by using the <a>bracketed range notation</a>
 	or in the property description,
-	then <code>[&minus;&infin;,&infin;]</code> is assumed.
+	then <code>[&minus;∞,∞]</code> is assumed.
 
-	Values of &minus;&infin; or &infin; must be written without units,
+	Values of &minus;∞ or ∞ must be written without units,
 	even if the value type uses units.
 	Values of ''0'' <em>can</em> be written without units,
 	even if the value type doesn't allow “unitless zeroes”
@@ -839,7 +843,7 @@ Range Restrictions and Range Definition Notation</h3>
 	any range limitations are described only in prose.
 	(For example, “Negative values are not allowed” or
 	“Negative values are invalid”
-	indicate a <code>[0,&infin;]</code> range.)
+	indicate a <code>[0,∞]</code> range.)
 	This does not make them any less binding.
 
 <!--
@@ -1333,7 +1337,6 @@ Viewport-percentage Lengths: the ''vw'', ''vh'', ''vmin'', ''vmax'' units</h4>
 	css/css-values/vh-support-transform-origin.html
 	css/css-values/vh-support-transform-translate.html
 	css/css-values/vh-zero-support.html
-	css/css-values/vh_not_refreshing_on_chrome.html
 	css/css-values/viewport-relative-lengths-scaled-viewport.html
 	css/css-values/viewport-unit-011.html
 	css/css-values/viewport-units-css2-001.html
@@ -1414,7 +1417,7 @@ Absolute Lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	are sometimes written like <code>2p3</code>,
 	indicating a length of 2 picas and 3 points.
 	These can be written in CSS as ''calc(2pc + 3pt)''
-	(see [[#calc-notation]]).
+	(see [[#calc-func]]).
 
 	All of the absolute length units are <a>compatible</a>,
 	and ''px'' is their <a>canonical unit</a>.
@@ -1476,7 +1479,7 @@ Absolute Lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	results in a reference pixel of 1.3&nbsp;mm.
 
 	<figure>
-		<img src="images/pixel1.png"
+		<img src="images/pixel1.png" width="500" height="360"
 		     alt="This diagram illustrates how the definition of a pixel
 		          depends on the users distance from the viewing surface
 		          (paper or screen).
@@ -1500,7 +1503,7 @@ Absolute Lengths: the ''cm'', ''mm'', ''Q'', ''in'', ''pt'', ''pc'', ''px'' unit
 	(such as a printer).
 
 	<figure>
-		<img src="images/pixel2.png"
+		<img src="images/pixel2.png" width="412" height="321"
 		     alt="This diagram illustrates the relationship between
 		          the reference pixel and device pixels (called “dots” below).
 		          The image depicts
@@ -1704,7 +1707,7 @@ Resolution Units: the <<resolution>> type and ''<resolution>/dpi'', ''<resolutio
 	or the 'image-resolution' property defined in [[CSS3-IMAGES]].
 
 	All <<resolution>> units are <a>compatible</a>,
-	and ''&lt;resolution>/dppx'' is their <a>canonical unit</a>.
+	and ''<resolution>/dppx'' is their <a>canonical unit</a>.
 
 	The allowed range of <<resolution>> values
 	<em>always</em> excludes negative values,
@@ -1865,7 +1868,7 @@ Functional Notations</h2>
  ███▌  █▌  █▌ █████  ███▌    ██ ██  
 -->
 
-<h3 id="calc-notation">
+<h3 id="calc-func" oldids="calc-notation">
 Mathematical Expressions: ''calc()''</h3>
 
 	The <dfn>calc()</dfn> function
@@ -2376,7 +2379,7 @@ Changes</h2>
 		(<a href="https://github.com/w3c/csswg-drafts/issues/7287">Issue 7287</a>)
 	* Cleaned up interaction of this specification and [[CSS-CASCADE-3]] in defining the [=CSS-wide keywords=].
 		(<a href="https://github.com/w3c/csswg-drafts/issues/7439">Issue 7439</a>)
-	* Removed definition of <<length-number>>, since it is impossible to combine them with ''calc()''.
+	* Removed definition of <css>&lt;length-number></css>, since it is impossible to combine them with ''calc()''.
 		(<a href="https://github.com/w3c/csswg-drafts/issues/2789">Issue 2789</a>)
 	* Fixed definition of [=numbers=] to allow decimals in combination with scientific notation,
 		as originally intended and as defined in [[CSS-SYNTAX-3]].