Fix bikeshed errors in color adjust spec (w3c#12155)

* fix bikeshed warnings

* clean up

* address feedback

Author: alisonmaher

css-color-adjust-1/Overview.bs

@@ -20,13 +20,20 @@ WPT Display: open
 </pre>
 <pre class='link-defaults'>
 spec:css2; type:dfn; text:canvas
+spec:css-backgrounds-3; type:property;
+	text:border-color
+	text:box-shadow
 spec:css-color-4; type:property; text:color
+spec:css-color-5; type:function; text:color()
 spec:fill-stroke-3; type:property;
 	text:fill
 	text:stroke
-spec: html; urlPrefix: https://html.spec.whatwg.org/multipage/; type: dfn;
-	text: navigable; for:Window; url: nav-history-apis.html#window-navigable
-	text: top-level traversable; for:/; url: document-sequences.html#top-level-traversable
+spec:css-gaps-1; type:property; text:column-rule-color
+spec: html;
+	text:body; type:element
+	text:meta; type:element
+	text:navigable; type:dfn; for:Window;
+	text:top-level traversable; type:dfn; for:/;
 </pre>
 
 <pre class=anchors>
@@ -57,7 +64,9 @@ Introduction {#intro}
 		to automatically adjust colors to the user's assumed performance preferences,
 		such as suppressing background colors when printing to save ink.
 
-	Together with the 'prefers-color-scheme', 'prefers-contrast', and 'forced-colors' [=media queries=] [[!MEDIAQUERIES-5]],
+	Together with the <a descriptor for=@media>prefers-color-scheme</a>,
+	<a descriptor for=@media>prefers-contrast</a>, and
+	<a descriptor for=@media>forced-colors</a> [=media queries=] [[!MEDIAQUERIES-5]],
 	this module allows color scheme negotiation
 	between the author and the user.
 
@@ -171,7 +180,7 @@ Opting Into a Preferred Color Scheme: the 'color-scheme' property {#color-scheme
 		rendering/dark-color-scheme/color-scheme-visited-link-initial.html
 	</wpt>
 
-	While the 'prefers-color-scheme' media feature
+	While the <a descriptor for=@media>prefers-color-scheme</a> media feature
 	allows an author to adapt the page’s colors to the user’s preferred color scheme,
 	many parts of the page are not under the author's control
 	(such as form controls, scrollbars, etc).
@@ -244,7 +253,7 @@ Opting Into a Preferred Color Scheme: the 'color-scheme' property {#color-scheme
 		To <dfn noexport>determine the used color scheme</dfn> of an element:
 
 		1. If the user's [=preferred color scheme=],
-			as indicated by the 'prefers-color-scheme' media feature,
+			as indicated by the <a descriptor for=@media>prefers-color-scheme</a> media feature,
 			is present among the listed [=color schemes=],
 			and is supported by the user agent,
 			that's the element's [=used color scheme=].
@@ -275,7 +284,7 @@ Opting Into a Preferred Color Scheme: the 'color-scheme' property {#color-scheme
 
 	<div class=example>
 		A page that responds to user preferences for light or dark display
-		by using the 'prefers-color-scheme' media feature
+		by using the <a descriptor for=@media>prefers-color-scheme</a> media feature
 		to alter the colors it uses
 		can easily opt the browser-controlled UI
 		(scrollbars, inputs, etc)
@@ -420,7 +429,7 @@ to conform to either a [=dark=] or [=light=] color scheme.
 	and have indicated so using the 'color-scheme' property
 	or <{meta/name/color-scheme}> <{meta}> name,
 	this has no effect other than reporting a ''@media/prefers-color-scheme/dark'' value
-	for the 'prefers-color-scheme' [=media query=]
+	for the <a descriptor for=@media>prefers-color-scheme</a> [=media query=]
 	and selecting a [=dark=] [=used color scheme=].
 
 	But for pages that do not explicitly support a [=dark=] color scheme,
@@ -788,7 +797,7 @@ Forced Color Palettes {#forced}
 <!--THOUGHTS
 	This advice (below) maybe makes sense for (prefers-contrast),
 	but is it really applicable to forced-colors as well?
-	If so, should forced-colors be instead a 'forced' value on 'prefers-contrast',
+	If so, should forced-colors be instead a 'forced' value on <a descriptor for=@media>prefers-contrast</a>,
 	so that a (prefers-contrast) query will catch all of these cases at once?
 
 	Authors are encouraged to simplify the contrast in their pages