W3C home > Mailing lists > Public > public-html-commits@w3.org > July 2008

html5/spec Overview.html,1.1110,1.1111

From: Ian Hickson via cvs-syncmail <cvsmail@w3.org>
Date: Wed, 23 Jul 2008 23:41:08 +0000
To: public-html-commits@w3.org
Message-Id: <E1KLnxE-00010x-5z@lionel-hutz.w3.org>

Update of /sources/public/html5/spec
In directory hutz:/tmp/cvs-serv3643

Modified Files:
	Overview.html 
Log Message:
more typos (whatwg r1921)

Index: Overview.html
===================================================================
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 Wednesday, 23 July 2008 23:41:41 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 9 October 2008 20:32:58 GMT