[e] (0) Reverse this set of cross-references to remove some ambiguity.

Fixing https://www.w3.org/Bugs/Public/show_bug.cgi?id=20711 Affected topics: DOM APIs, Rendering git-svn-id: http://svn.whatwg.org/webapps@7750 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Mar 13, 2013 · c5afba7 · c5afba7
1 parent 177f65a
commit c5afba7
Show file tree

Hide file tree

Showing 3 changed files with 9 additions and 6 deletions.
diff --git a/complete.html b/complete.html
@@ -9193,7 +9193,7 @@ <h4 id=elements-in-the-dom><span class=secno>3.2.2 </span>Elements in the DOM</h
   specification. This includes <a href=#html-elements>HTML elements</a> in <a href=#xml-documents>XML documents</a>, even when
   those documents are in another context (e.g. inside an XSLT transform).</p>
 
-  <p>Elements in the DOM <a href=#represents title=represents>represent</a> things; that is, they have
+  <p>Elements in the DOM <dfn id=represents title=represents>represent</dfn> things; that is, they have
   intrinsic <em>meaning</em>, also known as semantics.</p>
 
   <p class=example>For example, an <code><a href=#the-ol-element>ol</a></code> element represents an ordered list.</p>
@@ -92596,6 +92596,7 @@ <h2 id=rendering><span class=secno>14 </span>Rendering</h2>
 
   <h3 id=introduction-13><span class=secno>14.1 </span>Introduction</h3>
 
+<!--CLEANUP-->
   <p>In general, user agents are expected to support CSS, and many of
   the suggestions in this section are expressed in CSS terms. User
   agents that use other presentation mechanisms can derive their
@@ -92605,7 +92606,7 @@ <h3 id=introduction-13><span class=secno>14.1 </span>Introduction</h3>
   <p>In the absence of style-layer rules to the contrary (e.g. author
   style sheets), user agents are expected to render an element so that
   it conveys to the user the meaning that the element
-  <dfn id=represents>represents</dfn>, as described by this specification.</p>
+  <span title=represent>represents</span>, as described by this specification.</p>
 
   <p>The suggestions in this section generally assume a visual output
   medium with a resolution of 96dpi or greater, but HTML is intended

diff --git a/index b/index
@@ -9193,7 +9193,7 @@ partial /*sealed*/ interface <dfn id=document>Document</dfn> {
   specification. This includes <a href=#html-elements>HTML elements</a> in <a href=#xml-documents>XML documents</a>, even when
   those documents are in another context (e.g. inside an XSLT transform).</p>
 
-  <p>Elements in the DOM <a href=#represents title=represents>represent</a> things; that is, they have
+  <p>Elements in the DOM <dfn id=represents title=represents>represent</dfn> things; that is, they have
   intrinsic <em>meaning</em>, also known as semantics.</p>
 
   <p class=example>For example, an <code><a href=#the-ol-element>ol</a></code> element represents an ordered list.</p>
@@ -92596,6 +92596,7 @@ document.body.appendChild(text);
 
   <h3 id=introduction-13><span class=secno>14.1 </span>Introduction</h3>
 
+<!--CLEANUP-->
   <p>In general, user agents are expected to support CSS, and many of
   the suggestions in this section are expressed in CSS terms. User
   agents that use other presentation mechanisms can derive their
@@ -92605,7 +92606,7 @@ document.body.appendChild(text);
   <p>In the absence of style-layer rules to the contrary (e.g. author
   style sheets), user agents are expected to render an element so that
   it conveys to the user the meaning that the element
-  <dfn id=represents>represents</dfn>, as described by this specification.</p>
+  <span title=represent>represents</span>, as described by this specification.</p>
 
   <p>The suggestions in this section generally assume a visual output
   medium with a resolution of 96dpi or greater, but HTML is intended

diff --git a/source b/source
@@ -9057,7 +9057,7 @@ partial /*sealed*/ interface <dfn>Document</dfn> {
   specification. This includes <span>HTML elements</span> in <span>XML documents</span>, even when
   those documents are in another context (e.g. inside an XSLT transform).</p>
 
-  <p>Elements in the DOM <span title="represents">represent</span> things; that is, they have
+  <p>Elements in the DOM <dfn title="represents">represent</dfn> things; that is, they have
   intrinsic <em>meaning</em>, also known as semantics.</p>
 
   <p class="example">For example, an <code>ol</code> element represents an ordered list.</p>
@@ -108402,6 +108402,7 @@ document.body.appendChild(text);
 
   <h3>Introduction</h3>
 
+<!--CLEANUP-->
   <p>In general, user agents are expected to support CSS, and many of
   the suggestions in this section are expressed in CSS terms. User
   agents that use other presentation mechanisms can derive their
@@ -108411,7 +108412,7 @@ document.body.appendChild(text);
   <p>In the absence of style-layer rules to the contrary (e.g. author
   style sheets), user agents are expected to render an element so that
   it conveys to the user the meaning that the element
-  <dfn>represents</dfn>, as described by this specification.</p>
+  <span title="represent">represents</span>, as described by this specification.</p>
 
   <p>The suggestions in this section generally assume a visual output
   medium with a resolution of 96dpi or greater, but HTML is intended