spec/Overview.html 1.1111 1921 more typos (whatwg r1921)

more typos (whatwg r1921)

8.2.7 Coercing an HTML DOM into an infoset
http://people.w3.org/mike/diffs/html5/spec/Overview.1.1111.html#coercing

http://people.w3.org/mike/diffs/html5/spec/Overview.diff.html
http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.1110&r2=1.1111&f=h
http://html5.org/tools/web-apps-tracker?from=1920&to=1921

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.1110
retrieving revision 1.1111
diff -u -d -r1.1110 -r1.1111
--- Overview.html 23 Jul 2008 23:39:35 -0000 1.1110
+++ Overview.html 23 Jul 2008 23:41:05 -0000 1.1111
@@ -51183,13 +51183,13 @@
 
   <p class=example>As another example, consider the attribute
    <code>xlink:href</code>. Used on a MathML element, it becomes, after being
-   <span title="adjust foreign attributes</span>, an attribute with a prefix
-   "><code title="">xlink</code>" and a local name "<code
-   title="">href</code>". However, used on an HTML element, it becomes an
-   attribute with no prefix and the local name "<code
+   <a href="#adjust" title="adjust foreign attributes">adjusted</a>, an
+   attribute with a prefix "<code title="">xlink</code>" and a local name
+   "<code title="">href</code>". However, used on an HTML element, it becomes
+   an attribute with no prefix and the local name "<code
    title="">xlink:href</code>", which is not a valid NCName, and thus might
    not be accepted by an XML API. It could thus get converted, becoming
-   "<code title="">xlinkU0003Ahref</code>".</span>
+   "<code title="">xlinkU0003Ahref</code>".
 
   <p class=note>The resulting names from this conversion conveniently can't
    clash with any attribute generated by the <a href="#html-0">HTML

Received on Thursday, 24 July 2008 07:31:56 UTC