[cssom][cssom-view] Editorial: Fix validation issues

Author: zcorpan

cssom-view/Overview.bs

@@ -465,7 +465,7 @@ When the <dfn method for=Window>matchMedia(<var>query</var>)</dfn> method is inv
  <li>Return a new {{MediaQueryList}} object,
  with the <a>context object’s</a>
  <a>associated <code>Document</code></a>
- as the <a concept>document</a>,
+ as the <a for=MediaQueryList>document</a>,
  with <var>parsed media query list</var> as its associated <a>media query list</a>.
 </ol>
 
@@ -705,13 +705,13 @@ The {{MediaQueryList}} Interface {#the-mediaquerylist-interface}
 This section integrates with the <a spec=html>event loop</a> defined in HTML. [[!HTML]]
 
 A {{MediaQueryList}} object has an associated <dfn>media query list</dfn>
-and an associated <dfn concept for=MediaQueryList>document</dfn> set on creation.
+and an associated <dfn for=MediaQueryList>document</dfn> set on creation.
 
-A {{MediaQueryList}} object has an associated <dfn concept for=MediaQueryList>media</dfn> which is the
+A {{MediaQueryList}} object has an associated <dfn for=MediaQueryList>media</dfn> which is the
 <a lt='serialize a media query list'>serialized</a> form of the associated <a>media query list</a>.
 
-A {{MediaQueryList}} object has an associated <dfn concept for=MediaQueryList>matches state</dfn> which is
-true if the associated <a>media query list</a> matches the state of the <a concept>document</a>, and false otherwise.
+A {{MediaQueryList}} object has an associated <dfn for=MediaQueryList>matches state</dfn> which is
+true if the associated <a>media query list</a> matches the state of the <a for=MediaQueryList>document</a>, and false otherwise.
 
 <!--XXX update the matches state when flushing layout (offsetWidth et al), without firing a change event. -->
 
@@ -721,18 +721,18 @@ When asked to <dfn>evaluate media queries and report changes</dfn> for a {{Docum
 
  <li>
 
-  For each {{MediaQueryList}} object <var>target</var> that has <var>doc</var> as its <a concept>document</a>,
+  For each {{MediaQueryList}} object <var>target</var> that has <var>doc</var> as its <a for=MediaQueryList>document</a>,
   in the order they were created, oldest first, run these substeps:
 
   <ol>
 
-   <li>If <var>target</var>'s <a concept>matches state</a> has changed since the last time these steps were run,
+   <li>If <var>target</var>'s <a>matches state</a> has changed since the last time these steps were run,
    <a>dispatch</a> a new <a>event</a> to <var>target</var>
    using the {{MediaQueryList}} interface,
    with its {{Event/type}} attribute initialized to <a event>change</a>,
    its {{Event/isTrusted}} attribute initialized to true,
-   its {{MediaQueryList/media}} attribute initialized to <var>target</var>'s <a concept>media</a>,
-   and its {{MediaQueryListEvent/matches}} attribute initialized to <var>target</var>'s <a concept>matches state</a>. <!--fingerprint-->
+   its {{MediaQueryList/media}} attribute initialized to <var>target</var>'s <a>media</a>,
+   and its {{MediaQueryListEvent/matches}} attribute initialized to <var>target</var>'s <a>matches state</a>. <!--fingerprint-->
 
   </ol>
 
@@ -764,10 +764,10 @@ interface MediaQueryList : EventTarget {
 </pre>
 
 The <dfn attribute for=MediaQueryList>media</dfn> attribute must return
-the associated <a concept>media</a>.
+the associated <a>media</a>.
 
 The <dfn attribute for=MediaQueryList>matches</dfn> attribute must return
-the associated <a concept>matches state</a>. <!--fingerprint-->
+the associated <a>matches state</a>. <!--fingerprint-->
 
 The <dfn method for=MediaQueryList>addListener(<var>listener</var>)</dfn> method must run these steps:
 
@@ -842,7 +842,7 @@ The <dfn attribute for=MediaQueryListEvent>matches</dfn> attribute must return t
    <td><dfn event for=MediaQueryList>change</dfn>
    <td>{{Event}}
    <td>{{MediaQueryList}}
-   <td>Fired at the {{MediaQueryList}} when the <a concept>matches state</a> changes.
+   <td>Fired at the {{MediaQueryList}} when the <a>matches state</a> changes.
 </table>
 
 The {{Screen}} Interface {#the-screen-interface}

cssom/Overview.bs

@@ -1042,12 +1042,12 @@ thoughts:
 
 ### The HTTP Default-Style Header ### {#the-http-default-style-header}
 
-The HTTP <code lt="http-default-style">Default-Style</code> header
+The HTTP <a lt="http-default-style">Default-Style</a> header
 can be used to set the <a>preferred CSS style sheet set name</a>
 influencing which <a>CSS style sheet set</a> is (initially) the
 <a>enabled CSS style sheet set</a>.
 
-For each HTTP <code lt="http-default-style">Default-Style</code>
+For each HTTP <a lt="http-default-style">Default-Style</a>
 header, in header order, the user agent must
 <a>change the preferred CSS style sheet set name</a> with name being the
 value of the header.
@@ -1463,10 +1463,10 @@ To <dfn>serialize a CSS rule</dfn>, perform one of the following in accordance w
  <dd>The literal string "<code>@namespace</code>", followed by a single SPACE
  (U+0020), followed by the
  <a lt="serialize an identifier">identifier escaped</a> value of the
- <code lt="dom-CSSNamespaceRule-prefix">prefix</code> attribute (if
+ {{CSSNamespaceRule/prefix}} attribute (if
  any), followed by a single SPACE (U+0020) if there is a prefix, followed by the
  <a lt="serialize a URL">URL escaped</a> value of the
- <code lt="dom-CSSNamespaceRule-namespaceURI">namespaceURI</code>
+ {{CSSNamespaceRule/namespaceURI}}
  attribute, followed the character "<code>;</code>" (U+003B).
 </dl>
 
@@ -2149,7 +2149,7 @@ result of invoking {{CSSStyleDeclaration/getPropertyValue()}} with the
 argument being the result of running the <a>IDL attribute to CSS property</a>
 algorithm for <var>camel-cased attribute</var>.
 
-Setting the <code attribute for=CSSStyleDeclaration><var>camel-cased attribute</var></code> attribute must invoke
+Setting the <a attribute for=CSSStyleDeclaration><var>camel-cased attribute</var></a> attribute must invoke
 {{CSSStyleDeclaration/setProperty()}} with the
 first argument being the result of running the <a>IDL attribute to CSS property</a>
 algorithm for <var>camel-cased attribute</var>, as second argument the given value, and no third argument. Any
@@ -2173,7 +2173,7 @@ getting, must return the result of invoking {{CSSStyleDeclaration/getPropertyVal
 argument being the result of running the <a>IDL attribute to CSS property</a> algorithm for
 <var>webkit-cased attribute</var>, with the <i>dash prefix</i> flag set.
 
-Setting the <code attribute for=CSSStyleDeclaration><var>webkit-cased attribute</var></code>
+Setting the <a attribute for=CSSStyleDeclaration><var>webkit-cased attribute</var></a>
 attribute must invoke {{CSSStyleDeclaration/setProperty()}} with the first argument being the result
 of running the <a>IDL attribute to CSS property</a> algorithm for <var>webkit-cased attribute</var>,
 with the <i>dash prefix</i> flag set, as second argument the given value, and no third argument.
@@ -2197,7 +2197,7 @@ The <dfn attribute for=CSSStyleDeclaration><var>dashed attribute</var></dfn> att
 result of invoking {{CSSStyleDeclaration/getPropertyValue()}} with the
 argument being <var>dashed attribute</var>.
 
-Setting the <code attribute for=CSSStyleDeclaration><var>dashed attribute</var></code> attribute must invoke
+Setting the <a attribute for=CSSStyleDeclaration><var>dashed attribute</var></a> attribute must invoke
 {{CSSStyleDeclaration/setProperty()}} with the
 first argument being <var>dashed attribute</var>, as second argument the given value, and no third argument. Any
 exceptions thrown must be re-thrown.
@@ -2652,11 +2652,11 @@ The <dfn method for=CSS>escape(<var>ident</var>)</dfn> method must return the re
 Resolved Values {#resolved-values}
 ==================================
 
-<code lt="dom-Window-getComputedStyle()">getComputedStyle()</code> was
+{{Window/getComputedStyle()}} was
 historically defined to return the "computed value" of an element or
 pseudo-element. However, the concept of "computed value" changed between
 revisions of CSS while the implementation of
-<code lt="dom-Window-getComputedStyle()">getComputedStyle()</code> had to
+{{Window/getComputedStyle()}} had to
 remain the same for compatibility with deployed scripts. To address this
 issue this specification introduces the concept of a
 <dfn>resolved value</dfn>.