[css-values] fix some linking errors

Author: tabatkins

css-values/Overview.bs

@@ -1804,10 +1804,10 @@ Toggling Between Values: ''toggle()''</h3>
 
 	<div class='example'>
 		The following example cycles markers for nested lists,
-		so that a top level list has ''disc''-shaped markers,
-		but nested lists use ''list-style-type/circle'', then ''square'', then ''box'',
+		so that a top level list has ''list-style-type/disc''-shaped markers,
+		but nested lists use ''list-style-type/circle'', then ''list-style-type/square'', then ''list-style-type/box'',
 		and then repeat through the list of marker shapes,
-		starting again (for the 5th list deep) with ''disc''.
+		starting again (for the 5th list deep) with ''list-style-type/disc''.
 
 		<pre>ul { list-style-type: toggle(disc, circle, square, box); }</pre>
 	</div>
@@ -2012,8 +2012,8 @@ Ian's proposal:
 
 	The <<type-or-unit>> keywords are:
 
-	<dl>
-		<dt>''string''
+	<dl dfn-type=value dfn-for="<type-or-value>">
+		<dt><dfn>string</dfn>
 		<dd>
 			The attribute value is taken as the contents of a CSS <<string>>.
 			The default is the empty string.
@@ -2022,13 +2022,13 @@ Ian's proposal:
 			So, for example, an attribute whose value is "\51" will produce a string containing those three characters,
 			not a string containing "Q" (the character that the escape would evaluate to).
 
-		<dt>''color''
+		<dt><dfn>color</dfn>
 		<dd>
 			The attribute value must parse as a HASH or IDENT CSS token,
 			and be successfully interpreted as a <<color>>.
 			The default is ''currentcolor''.
 
-		<dt>''url''
+		<dt><dfn>url</dfn>
 		<dd>
 			The attribute value is taken as the contents of a CSS <<string>>.
 			It is interpreted as a quoted string within the ''url()'' notation.
@@ -2038,7 +2038,7 @@ Ian's proposal:
 			according to the rules of the document language as applied to URLs originating from the element;
 			they are not relative to the style sheet.
 
-		<dt>''integer''
+		<dt><dfn>integer</dfn>
 		<dd>
 			The attribute value must parse as a NUMBER CSS token,
 			and be successfully interpreted as an <<integer>>.
@@ -2048,7 +2048,7 @@ Ian's proposal:
 			if the property in question only accepts integers within a certain range
 			and the attribute is out of range.
 
-		<dt>''number''
+		<dt><dfn>number</dfn>
 		<dd>
 			The attribute value must parse as a NUMBER CSS token,
 			and is interpreted as an <<number>>.
@@ -2058,10 +2058,10 @@ Ian's proposal:
 			if the property in question only accepts integers within a certain range
 			and the attribute is out of range.
 
-		<dt>''length''
-		<dt>''angle''
-		<dt>''time''
-		<dt>''frequency''
+		<dt><dfn>length</dfn>
+		<dt><dfn>angle</dfn>
+		<dt><dfn>time</dfn>
+		<dt><dfn>frequency</dfn>
 		<dd>
 			The attribute value must parse as a DIMENSION CSS token,
 			and be successfully interpreted as the specified type.
@@ -2073,7 +2073,7 @@ Ian's proposal:
 			and the attribute is out of range (e.g. a negative length or 180deg).
 			If the unit is a relative length, it must be computed to an absolute length.
 
-		<dt>''%''
+		<dt><dfn>%</dfn>
 		<dt>A keyword matching one of the <<length>>, <<angle>>, <<time>>, or <<frequency>> units
 		<dd>
 			The attribute value must parse as a NUMBER CSS token,