[css-properties-values] Fix linking.

Author: tabatkins

css-properties-values-api/Overview.bs

@@ -35,7 +35,6 @@ Repository: w3c/css-houdini-drafts
 
 <pre class='link-defaults'>
 spec:css-transforms-1; type:type; text:<transform-function>
-spec:css-conditional-3; type:method; text:supports(property, value)
 spec:cssom-1; type:interface; text:CSS
 </pre>
 
@@ -91,7 +90,7 @@ following members:
 ::  True if this custom property should inherit down the DOM tree; False otherwise.
 
 :   <dfn dict-member for=PropertyDescriptor>initialValue</dfn>
-::  The initial value of this custom property. 
+::  The initial value of this custom property.
 
 The {{registerProperty()}} function {#the-registerproperty-function}
 --------------------------------------------------------------------
@@ -120,19 +119,19 @@ not parseable using the provided {{PropertyDescriptor/syntax}} must cause it to
 throw a {{SyntaxError}}. If no {{PropertyDescriptor/initialValue}} is provided and the
 {{PropertyDescriptor/syntax}} is '*', then a special initial value used. This initial
 value must be considered parseable by {{registerProperty()}} but invalid at computed
-value time. Initial values that are not computationally idempotent must also cause 
+value time. Initial values that are not computationally idempotent must also cause
 {{registerProperty()}} to throw a {{SyntaxError}}.
 
 <div class='example'>
 For example, "3cm" is a computationally idempotent length, and hence valid as an initial value.
 However, "3em" is not (depending on the environment, 3em could compute to
-multiple different values). Additionally, "var(--foo)" is not computationally idempotent. 
+multiple different values). Additionally, "var(--foo)" is not computationally idempotent.
 </div>
 
 Issue: define computational idempotency.
 
 Issue(121): Is computational idempotency the right thing to do here? We could also just
-resolve any relative values once (against all the other initial values) and use 
+resolve any relative values once (against all the other initial values) and use
 that. OR! We could allow specified values and just fix our engines...
 
 When a custom property is registered with a given type, the process via which specified
@@ -161,7 +160,7 @@ are valid. Hence, the result of this stylesheet:
 <pre class='lang-css'>
 .thing {
   --my-color: green;
-  --my-color: url("not-a-color"); 
+  --my-color: url("not-a-color");
   color: var(--my-color);
 }
 </pre>
@@ -318,7 +317,7 @@ this is standard across implementations to avoid interop issues.
 Conditional Rules {#conditional-rules}
 --------------------------------------
 
-@supports rules and the <a method for=CSS>supports()</a> method behave as specified
+''@supports'' rules and the {{CSS/supports(conditionText)}} method behave as specified
 in [[!css-variables]].
 
 Note: In other words, for the purpose of determining whether a value is