[css-ui-4][editorial] Fix bikeshed errors

Author: tabatkins

css-ui-4/Overview.bs

@@ -101,6 +101,41 @@ spec:css-backgrounds-3; type:property; text:border-top-color
 spec:css-backgrounds-3; type:property; text:border-right-color
 spec:css-backgrounds-3; type:property; text:border-bottom-color
 spec:css-backgrounds-3; type:property; text:border-left-color
+spec:css-borders-4; type:property;
+	text:box-shadow
+	text:border-top-style
+	text:border-left-style
+	text:border-right-style
+	text:border-bottom-style
+	text:border-top-width
+	text:border-left-width
+	text:border-right-width
+	text:border-bottom-width
+	text:border-top-color
+	text:border-left-color
+	text:border-right-color
+	text:border-bottom-color
+	text:border-start-start-radius
+	text:border-start-end-radius
+	text:border-end-start-radius
+	text:border-end-end-radius
+	text:border-top-left-radius
+	text:border-top-right-radius
+	text:border-bottom-left-radius
+	text:border-bottom-right-radius
+	text:border-block-start-width
+	text:border-block-end-width
+	text:border-inline-start-width
+	text:border-inline-end-width
+	text:border-block-start-style
+	text:border-block-end-style
+	text:border-inline-start-style
+	text:border-inline-end-style
+	text:border-block-start-color
+	text:border-block-end-color
+	text:border-inline-start-color
+	text:border-inline-end-color
+spec:dom; type:dfn; text:element
 </pre>
 <pre class=anchors>
 urlPrefix: https://html.spec.whatwg.org/multipage/; spec:HTML
@@ -972,7 +1007,7 @@ Predefined Cursors</h5>
 			<dd>Indicates that the requested action will not be carried out.
 				Often rendered as a circle with a line through it.
 
-			<dt><dfn style="cursor:grab">grab</dfn>
+			<dt><dfn caniuse=css3-cursors-grab style="cursor:grab">grab</dfn>
 			<dd>Indicates that something can be grabbed (dragged to be moved).
 				Often rendered as the backside of an open hand.
 			<dt><dfn style="cursor:grabbing">grabbing</dfn>
@@ -1044,7 +1079,7 @@ Cursor of the canvas</h5>
 	boxes are generated for it and its cursor is used for the canvas.
 
 
-<h3 id="insertion-caret">
+<h3 id="the-insertion-caret">
 Insertion caret</h3>
 
 	The <dfn lt="insertion caret|caret">insertion caret</dfn> (or “caret” for short)
@@ -1056,7 +1091,7 @@ Insertion caret</h3>
 	Text or elements are considered to <dfn>accept text input</dfn>
 	if they are either an [=editable element=] or a descendent thereof,
 	excluding any such element where the [=used value=] of 'user-select' is ''user-select/none'',
-	as well as subtrees rooted at an HTML element with a {{ElementContentEditable/contentEditable}} attribute set to {{ElementContentEditable/contentEditable/false}}.
+	as well as subtrees rooted at an HTML element with a {{ElementContentEditable/contentEditable}} attribute set to <code>false</code>.
 
 	Some user agents have other user interface mechanisms
 	with a similar appearance,
@@ -1535,12 +1570,12 @@ Directional Focus Navigation: the 'nav-up', 'nav-right', 'nav-down', 'nav-left'
 			The &lt;target-name&gt; parameter indicates the target frame for the focus navigation.
 			It is a <<string>> and it MUST NOT start with the underscore "_" character.
 			Error handling: if it does start with an underscore, "_parent" navigates to the parent frame,
-			"_root" is treated as ''root'',
+			"_root" is treated as ''nav-up/root'',
 			and other values navigate to a frame by that name if it exists.
 			If the specified target frame does not exist,
-			the parameter will be treated as the keyword ''current'',
+			the parameter will be treated as the keyword ''nav-up/current'',
 			which means to simply use the frame that the element is in.
-			The keyword ''root'' indicates that the user agent should target the full window.
+			The keyword ''nav-up/root'' indicates that the user agent should target the full window.
 	</dl>
 
 	User agents for devices with directional navigation keys
@@ -1987,28 +2022,28 @@ Animation type: discrete
 </pre>
 
 The 'interactivity' property specifies whether an element and its [=flat tree=] descendants
-(including [=text runs=])
+(including [=text nodes=])
 are [=inert=] or not.
 
 <dl dfn-type=value dfn-for=interactivity>
 	: <dfn>auto</dfn>
-	:: The element's [=inert|inertness=] is determined by the [=host language=].
+	:: The element's [=inert|inertness=] is determined by the <l spec=selectors-4>[=host language=]</l>.
 		<span class=note>(This will <em>usually</em> mean the element is not [=inert=].)</span>
 
 	: <dfn>inert</dfn>
 	:: The element is [=inert=].
 </dl>
 
 <div algorithm>
-	When an [=element=] or [=text run=] is <dfn export>inert</dfn>:
+	When an [=/element=] or [=text node=] is <dfn export>inert</dfn>:
 
-	* Hit-testing must act as if 'pointer-event' was ''pointer-events/none'',
+	* Hit-testing must act as if 'pointer-events' was ''pointer-events/none'',
 		regardless of its actual value.
 	* Text selection must act as if 'user-select' was ''user-select/none'',
 		regardless of its actual value.
-	* If the [=element=] or [=text run=] is editable,
+	* If the [=/element=] or [=text node=] is editable,
 		it must behave as if it was non-editable.
-	* The [=element=] or [=text run=] should be ignored
+	* The [=/element=] or [=text node=] should be ignored
 		for the purposes of find-in-page and similar searching actions.
 
 	User agents may allow the user 
@@ -2212,7 +2247,7 @@ Switching appearance: the 'appearance' property</h3>
 	<a>widgets</a> are typically rendered by UAs using native UI controls of the host operating system,
 	which can neither be replicated nor styled using CSS.
 
-	The term <dfn export>widget</dfn> in this specification denotes [=replaced=] elements that can have <dfn export>native appearance</dfn>,
+	The term <dfn export>widget</dfn> in this specification denotes [=replaced=] elements that can have <dfn export lt="native appearance|native render|natively render">native appearance</dfn>,
 	meaning that they are rendered like analogous native widgets or controls of the host operating system or platform,
 	or with a look and feel not otherwise expressible in CSS.
 	It is up to the host language (e.g., HTML [[HTML]]) to define which elements can have <a>native appearance</a>.
@@ -2418,28 +2453,29 @@ Switching appearance: the 'appearance' property</h3>
 	to ensure that the intended appearance is preserved,
 	or because these properties may not be meaningful for the chosen appearance.
 
-	<dfn>Disregarding</dfn> a property means that
+	<dfn lt="disregard">Disregarding</dfn> a property means that
 	the user agent treats it as if it didn't [=apply to=] the widget in question.
 	Nevertheless,
 	unless an explicit exception is specified (for compatibility reasons),
 	the user agent must still determine the [=computed value=] of any [=disregarded=] property
 	according to the usual rules.
 
-  In more detail, the rules for disregarding properties for [=natively rendered=] widgets are:
+	In more detail, the rules for disregarding properties for [=natively rendered=] widgets are:
+
 	<ul>
-  	<li>	CSS properties that impact the box sizing or position of the widget's box (such as the [=sizing properties=]),
-	or their visual appearance outside of the box (such as 'transform', 'filter' or 'box-shadow'), must be applied to
-	 [=widgets=] rendered with their [=native appearance=]. The widget's box participates in the rest of layout like any other replaced element.
-	  <li> Properties that affect the internal box model sizing of the widget's box (such as 'box-sizing', 'padding', 'border' or 'margin') may be disregarded when needed.
-	  <li> Other properties that affect painting (like 'background-color') may be disregarded when needed.
-	  <li> User agents should take into account CSS properties that affect writing modes or font-related properties when possible,
+		<li>CSS properties that impact the box sizing or position of the widget's box (such as the [=sizing properties=]),
+			or their visual appearance outside of the box (such as 'transform', 'filter' or 'box-shadow'), must be applied to
+			[=widgets=] rendered with their [=native appearance=]. The widget's box participates in the rest of layout like any other replaced element.
+		<li> Properties that affect the internal box model sizing of the widget's box (such as 'box-sizing', 'padding', 'border' or 'margin') may be disregarded when needed.
+		<li> Other properties that affect painting (like 'background-color') may be disregarded when needed.
+		<li> User agents should take into account CSS properties that affect writing modes or font-related properties when possible,
 	when rendering text within the widget.
-	  <li> The 'object-fit' property does not apply.
+		<li> The 'object-fit' property does not apply.
 	</ul>
 
 	<div class=example>
-	  Some user agents respect the 'border' and 'padding' CSS properties for a &lt;select&gt; rendered with [=native appearance=], but
-	  not for &lt;input type=checkbox&gt;.
+		Some user agents respect the 'border' and 'padding' CSS properties for a &lt;select&gt; rendered with [=native appearance=], but
+		not for &lt;input type=checkbox&gt;.
 	</div>
 
 	Native rendering of widgets may overflow the size of its box if its intrinsic sizing exceeds that size.