mike: clarify in Abstract that we also include info from "other sources" (e.g,, default UA stylesheet for WebKit) (bug 10083)

mike: clarify in Abstract that we also include info from "other sources"
(e.g,, default UA stylesheet for WebKit) (bug 10083)
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10083

http://dev.w3.org/cvsweb/html5/markup/spec.html?r1=1.235&r2=1.236&f=h

===================================================================
RCS file: /sources/public/html5/markup/Overview.html,v
retrieving revision 1.430
retrieving revision 1.431
diff -u -d -r1.430 -r1.431
--- Overview.html 7 Jul 2010 08:04:56 -0000 1.430
+++ Overview.html 7 Jul 2010 08:18:04 -0000 1.431
@@ -45,8 +45,8 @@
       <a href="http://dev.w3.org/html5/spec/">HTML5: A vocabulary and associated APIs for HTML and XHTML</a>
       specification
       <a href="references.html#refsHTML5">[HTML5]</a>,
-      as well as information in other deliverables published by
-      the HTML Working Group.
+      as well as information in related deliverables published by
+      the HTML Working Group and from other sources.
       By design, this reference does not describe related APIs in detail,
       nor attempt to explain how implementations that are
       consumers of HTML content are meant to process documents

Index: spec.html
===================================================================
RCS file: /sources/public/html5/markup/spec.html,v
retrieving revision 1.235
retrieving revision 1.236
diff -u -d -r1.235 -r1.236
--- spec.html 7 Jul 2010 08:04:57 -0000 1.235
+++ spec.html 7 Jul 2010 08:18:05 -0000 1.236
@@ -44,8 +44,8 @@
       <a href="http://dev.w3.org/html5/spec/">HTML5: A vocabulary and associated APIs for HTML and XHTML</a>
       specification
       <a href="references.html#refsHTML5">[HTML5]</a>,
-      as well as information in other deliverables published by
-      the HTML Working Group.
+      as well as information in related deliverables published by
+      the HTML Working Group and from other sources.
       By design, this reference does not describe related APIs in detail,
       nor attempt to explain how implementations that are
       consumers of HTML content are meant to process documents

Received on Wednesday, 7 July 2010 08:18:46 UTC