[css-cascade-5][editorial] Fixed Bikeshed issues

Author: SebastianZ

css-cascade-5/Overview.bs

@@ -28,16 +28,31 @@ Informative Classes: ex
 </pre>
 
 <pre class=link-defaults>
-spec:dom; type:dfn; text:shadow tree
+spec:css-2025; type:dfn; text:vendor-prefixed
+spec:css-backgrounds-3;
+	type:property;
+		text:border
+		text:border-color
+		text:border-image
+		text:border-style
+		text:border-bottom-width
+		text:border-left-width
+		text:border-right-width
+		text:border-top-width
+	type:value; for:border-style; text:dotted
 spec:css-color-4; type:property; text:color
+spec:css-conditional-3; type:at-rule; text:@media
 spec:css-values-3; type: value; text:ex
 spec:css-values-5; type: function; text:if()
-spec:css-conditional-3; type:at-rule; text:@media
-spec:mediaqueries-4; type:type; for:@media; text:all
-spec:mediaqueries-4; type:type; text:<media-query>
-spec:css-2021; type:dfn; text:vendor-prefixed
-spec:css-fonts-4; type:property; text:font-style
-spec:css-fonts-4; type:property; text:font-family
+spec:css-fonts-4; type:property;
+	text:font-family
+	text:font-size-adjust
+	text:font-style
+spec:dom; type:dfn; text:shadow tree
+spec:html; type:element; text:audio
+spec:mediaqueries-4; type:type;
+	for:@media; text:all
+	text:<media-query>
 </pre>
 
 <pre class=ignored-specs>
@@ -51,7 +66,7 @@ Introduction</h2>
 	CSS defines a finite set of parameters,
 	called <dfn export for=CSS lt="property">properties</dfn>,
 	that direct the rendering of a document.
-	Each [=property=] has a name
+	Each [=CSS/property=] has a name
 	(e.g., 'color', 'font-size', or 'border-style'),
 	a value space
 	(e.g., <<color>>, <<length-percentage>>, <css>[ solid | dashed | dotted | &hellip; ]</css>),
@@ -237,7 +252,7 @@ Conditional ''@import'' Rules</h3>
 
 	The [=import conditions=] are given by
 	<<media-query-list>>, which is parsed and interpreted as a <a>media query list</a>,
-	and <<supports-condition>>, is parsed and interpreted as a [[supports query]].
+	and <<supports-condition>>, is parsed and interpreted as a [=supports query=].
 	If a <<declaration>> is given in place of a <<supports-condition>>,
 	it must be interpreted as a <<supports-decl>>
 	(i.e. the extra set of parentheses is implied)
@@ -845,7 +860,7 @@ Per-Fragment Value Processing</h3>
 	Subsequent value processing proceeds as normal in each fragment.
 
 	APIs that assume a singular value per [=box=] (rather than per [=box fragment=])
-	must ignore the effects of non-[=tree-abiding=] [=pseudo-elements=].
+	must ignore the effects of non-[=tree-abiding pseudo-elements=].
 	(For example, ''::first-line'' styles have no effect on the value returned by {{getComputedStyle()}}.)
 
 	<div class=example>
@@ -1058,7 +1073,7 @@ Cascade Sorting Order</h3>
 
 			<ul>
 				<li>Style sheets are ordered
-					in [[final CSS style sheets]] order.
+					in [=final CSS style sheets=] order.
 				<li>Declarations from <a at-rule lt="@import">imported style sheets</a>
 					are ordered as if their style sheets were substituted in place of the ''@import'' rule.
 				<li>Declarations from style sheets independently linked by the originating document
@@ -1341,8 +1356,8 @@ Layer Naming and Nesting</h4>
 
 	<div class="example">
 		In this example,
-		the nested ''framework.base'' layer is distinct
-		from the top-level ''base'' layer:
+		the nested <css>framework.base</css> layer is distinct
+		from the top-level <css>base</css> layer:
 
 		<pre class='lang-css'>
 			@layer base {
@@ -1362,16 +1377,16 @@ Layer Naming and Nesting</h4>
 
 		The resulting layers can be represented as a tree:
 
-		1. ''base''
-		2. ''framework''
-			1. ''base''
-			2. ''theme''
+		1. <css>base</css>
+		2. <css>framework</css>
+			1. <css>base</css>
+			2. <css>theme</css>
 
 		or as a flat list with nested identifiers:
 
-		1. ''base''
-		2. ''framework.base''
-		3. ''framework.theme''
+		1. <css>base</css>
+		2. <css>framework.base</css>
+		3. <css>framework.theme</css>
 	</div>
 
 	Syntactically, an explicit [=layer name=] is represented
@@ -1896,7 +1911,7 @@ Rolling Back Cascade Origins: the ''revert'' keyword</h4>
 	reverting one of the paired properties in a [=logical property group=]
 	also reverts the other one; etc.
 
-<h4 id="revert-layer" caniuse="mdn-css_types_global_keywords_revert-layer">
+<h4 id="revert-layer">
 Rolling Back Cascade Layers: the ''revert-layer'' keyword</h4>
 
 	The <dfn value for=all>revert-layer</dfn> [=CSS-wide keyword=]
@@ -1985,7 +2000,6 @@ Rolling Back Rules: the ''revert-rule'' keyword</h4>
 		the above style sets ''border-radius'' to <code>0px</code>
 		only when the [=computed value=] of <code>--mode</code>
 		is <code>sharp</code>.
-		</pre>
 	</div>
 
 	The ''revert-rule'' keyword behaves like ''revert-layer''
@@ -2065,7 +2079,7 @@ Non-trivial changes since the <a href="CSS Cascading and Inheritance Level 5">13
 	* Added the ''revert-rule'' keyword.
 		(<a href="https://github.com/w3c/csswg-drafts/issues/10443">Issue 10443</a>)
 	* Clarify that all “aliases” of a property are reverted by ''revert''/''revert-layer''.
-	* Clarify that style sheets are ordered in [[final CSS style sheets]] order.
+	* Clarify that style sheets are ordered in [=final CSS style sheets=] order.
 	* Clarify that only ''@layer'' statement rules are ignored when checking validity of ''@import'', not empty ''@layer'' block rules.
 
 <h3 id="changes-2021-10">
@@ -2191,8 +2205,8 @@ Additions Since Level 2</h3>
 	and Boris Zbarsky
 	contributed to this specification.
 
-<h2 class=no-num id=priv-sec>
-Privacy and Security Considerations</h2>
+<h2 class=no-num id=privacy>
+Privacy Considerations</h2>
 
 	* The cascade process does not distinguish between same-origin and cross-origin stylesheets,
 		enabling the content of cross-origin stylesheets to be inferred
@@ -2202,12 +2216,15 @@ Privacy and Security Considerations</h2>
 		are exposed by the cascade process,
 		and can be inferred from the computed styles they apply to a document.
 
-	* The ''@import'' rule does not apply the [=CORS protocol=] to loading cross-origin stylesheets,
-		instead allowing them to be freely imported and applied.
-
 	* The ''@import'' rule assumes that resources without <a href="https://html.spec.whatwg.org/multipage/urls-and-fetching.html#content-type"><code>Content-Type</code> metadata</a>
 		(or any same-origin file if the host document is in quirks mode)
 		are <code>text/css</code>,
 		potentially allowing arbitrary files to be imported into the page
 		and interpreted as CSS,
 		potentially allowing sensitive data to be inferred from the computed styles they apply to a document.
+
+<h2 class=no-num id=security>
+Security Considerations</h2>
+
+	* The ''@import'' rule does not apply the [=CORS protocol=] to loading cross-origin stylesheets,
+		instead allowing them to be freely imported and applied.