[css-ui-3] Tweaks to get bikeshed to generate links correctly

Author: frivoal

css-ui/Overview.bs

@@ -37,13 +37,7 @@ Ignored Terms: ime-mode
 At Risk: Directional focus navigation: the 'nav-up', 'nav-right', 'nav-down', 'nav-left' properties
 </pre>
 <pre class=link-defaults>
-spec:css-backgrounds-3; type:property; text:border-width
-spec:css-backgrounds-3; type:property; text:border-style
-spec:css-backgrounds-3; type:property; text:border-bottom-width
-spec:css-backgrounds-3; type:property; text:border-left-width
-spec:css-backgrounds-3; type:property; text:border-right-width
-spec:css-backgrounds-3; type:property; text:border-top-width
-spec:css-backgrounds-3; type:property; text:background-image
+spec:css-overflow-3; type:property; text:overflow
 spec:css21; type:property; text:display
 </pre>
 
@@ -369,14 +363,12 @@ Note: This specification does not define the exact position or shape of the outl
 The 'outline-width' property accepts
 the same values as
           'border-width'
-([[!CSS3BG]],
-<a href="https://www.w3.org/TR/css3-background/#the-border-width">Section 4.3</a>).
+([[css-backgrounds-3#the-border-width]]).
 
 The 'outline-style' property accepts
 the same values as
           'border-style'
-([[!CSS3BG]],
-<a href="https://www.w3.org/TR/css3-background/#the-border-style">Section 4.2</a>),
+([[css-backgrounds-3#the-border-style]]),
 except that
 <span class=css>hidden</span> is not a legal outline style.
 In addition, in CSS3,
@@ -408,7 +400,7 @@ on platforms that do not support color inversion of the pixels on the screen.
 If the UA does not support the ''invert'' value
 then it must reject that value at parse-time, and
 the initial value of the 'outline-color' property
-is the ''color/currentColor'' [[!CSS3COLOR]] keyword.
+is the ''color/currentColor'' keyword.
 
 The 'outline' property is a shorthand property,
 and sets all three of 'outline-style',
@@ -555,7 +547,7 @@ The 'resize' property applies to elements
 whose computed 'overflow' value
 is something other than ''visible''.
 UAs may also apply it,
-regardless of the value of the ''overflow'' property,
+regardless of the value of the 'overflow' property,
 to:
 <ul>
 	<li>Replaced elements representing images or videos, such as <{img}>, <{video}>, <{picture}>, <{svg}>, <{object}>, or <{canvas}>.
@@ -659,11 +651,11 @@ Text can overflow for example when it is prevented from wrapping
 or a single word is too long to fit).
 Values have the following meanings:
 
-<dl data-dfn-for="overflow" class="valuedef">
-  <dt><dfn id=overflow-clip>clip</dfn></dt>
+<dl data-dfn-for="text-overflow" class="valuedef">
+  <dt><dfn id=overflow-clip dfn-type=value>clip</dfn></dt>
     <dd>Clip inline content that overflows its block container element. Characters may be only partially rendered.</dd>
 
-  <dt><dfn id=overflow-ellipsis>ellipsis</dfn></dt>
+  <dt><dfn id=overflow-ellipsis dfn-type=value>ellipsis</dfn></dt>
     <dd>
 Render an ellipsis character (U+2026)
 to represent clipped inline content.
@@ -913,7 +905,7 @@ Computed value: as specified, except with any relative URLs converted to absolut
 This property specifies the type of cursor to be displayed for the pointing device
 when the cursor's hotspot is within the element's <a>border edge</a>.
 
-Note: As per [[CSS3BG]], the <a>border edge</a> is affected by 'border-radius'.
+Note: As per [[css-backgrounds-3#the-border-radius]], the <a>border edge</a> is affected by 'border-radius'.
 
 In the case of overlapping elements,
 which element determines the type of cursor
@@ -946,15 +938,15 @@ Conforming User Agents may, instead of <<url>>, support <<image>> which is a sup
 The UA must support the following image file formats:
 <ul>
 	<li>PNG, as defined in [[!PNG]]
-	<li>SVG, as defined in [[!SVG]], in <a href="https://www.w3.org/TR/svg-integration/#secure-static-mode">secure static mode</a> [[!SVG-INTEGRATION]]
+	<li>SVG, as defined in [[!SVG11]], in <a href="https://www.w3.org/TR/svg-integration/#secure-static-mode">secure static mode</a> [[!SVG-INTEGRATION]]
 	<li>any other non-animated image file format that they support
 	for <<image>> in other properties,
 	such as the the 'background-image' property
 </ul>
 
 In addition, the UA should support the following image file formats:
 <ul>
-	<li>SVG, as defined in [[!SVG]], in <a href="https://www.w3.org/TR/svg-integration/#secure-animated-mode">secure animated mode</a> [[!SVG-INTEGRATION]]
+	<li>SVG, as defined in [[!SVG11]], in <a href="https://www.w3.org/TR/svg-integration/#secure-animated-mode">secure animated mode</a> [[!SVG-INTEGRATION]]
 	<li>any other animated image file format that they support
 	for <<image>> in other properties,
 	such as the the 'background-image' property
@@ -1168,7 +1160,7 @@ Here is an example of using several cursor values.
 </code></pre>
 
 This example sets the cursor on all hyperlinks (whether visited or not)
-to an external <a href="https://www.w3.org/TR/SVG/interact.html#CursorElement">SVG cursor</a> ([[SVG]], section 16.8.3).
+to an external <a href="https://www.w3.org/TR/SVG/interact.html#CursorElement">SVG cursor</a> ([[SVG11]], section 16.8.3).
 User agents that don't support SVG cursors would simply skip
 to the next value and attempt to use the "hyper.cur" cursor.
 If that cursor format was also not supported,