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

Author: SebastianZ

css-cascade-4/Overview.bs

@@ -31,19 +31,30 @@ Informative Classes: ex
 </pre>
 
 <pre class=link-defaults>
+spec:css-backgrounds-3;
+	type:property;
+		text:border
+		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-values-3; type: value; text:ex
 spec:css-color-4; type:property; text:color
 spec:css-conditional-3; type:at-rule; text:@media
 spec:css-fonts-4; type:property;
 	text:font-family
+	text:font-size-adjust
 	text:font-style
 spec:mediaqueries-4;
 	type:type; text:<media-query>
 	type:value; text:all; for:@media
-spec:css22; type:property; text:display
+spec:css-display-3; type:property; text:display
 spec:css-color-4; type:value; text:red
 spec:html; type:element; text:style
-spec:css-2021; type:dfn; text:vendor-prefixed
+spec:css-2025; type:dfn; text:vendor-prefixed
 spec:css-scoping-1; type:dfn; text:shadow tree
 </pre>
 
@@ -234,7 +245,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)
@@ -994,7 +1005,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
@@ -1325,7 +1336,7 @@ Non-trivial changes since the <a href="https://www.w3.org/TR/2022/CR-css-cascade
 
 <!-- to 11 Jan 2022  -->
 	* Clarify that all “aliases” of a property are reverted by ''revert''.
-	* Clarify that style sheets are ordered in [[final CSS style sheets]] order.
+	* Clarify that style sheets are ordered in [=final CSS style sheets=] order.
 
 <h3 id="changes-2021-10">
 Changes since the 15 Oct 2021 Working Draft</h3>
@@ -1418,7 +1429,7 @@ Changes Since the 14 January 2016 Candidate Recommendation</h3>
 				<dl>
 					<dt>user origin
 					<dd>
-						Rolls back the <del>cascade</del><ins><a>cascaded value</a><ins> to the user-agent level,
+						Rolls back the <del>cascade</del><ins><a>cascaded value</a></ins> to the user-agent level,
 						so that the <a>specified value</a> is calculated as if no author-level or user-level rules were specified for this property <ins>on this element</ins>.
 
 					<dt>author origin
@@ -1465,7 +1476,7 @@ Changes Since the 14 January 2016 Candidate Recommendation</h3>
 			as their properties are now observable distinct from their inline parent’s
 			via ''display: contents'' [[css-display-3]].
 			<blockquote>
-				<ins><p>For the purpose of this specification,
+				<ins>For the purpose of this specification,
 				<a>text nodes</a> are treated as <a spec=css-display-3>element</a> children of their associated element,
 				and possess the full set of properties;
 				since they cannot be targeted by selectors
@@ -1529,8 +1540,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
@@ -1540,12 +1551,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.