[e] (0) Update WHATWG abstract; update W3C header to match pubrules b…

…etter; fix links.

git-svn-id: http://svn.whatwg.org/webapps@1857 340c8d12-0b0e-0410-8428-c7bf67bfef74

header-whatwg

@@ -55,11 +55,13 @@
   <h2 class="no-num no-toc" id="abstract">Abstract</h2>
 
   <p>This specification evolves HTML and its related APIs to ease the
-  authoring of Web-based applications. Additions include the context
-  menus, a direct-mode graphics canvas, inline popup windows, and
-  server-sent events. Heavy emphasis is placed on keeping the language
-  backwards compatible with existing legacy user agents and on keeping
-  user agents backwards compatible with existing legacy documents.</p>
+  authoring of Web-based applications. Additions include context
+  menus, a direct-mode graphics canvas, a full duplex client-server
+  communication channel, more semantics, audio and video, various
+  features for offline Web applications, sandboxed iframes, and scoped
+  styling. Heavy emphasis is placed on keeping the language backwards
+  compatible with existing legacy user agents and on keeping user
+  agents backwards compatible with existing legacy documents.</p>
 
 
   <h2 class="no-num no-toc" id="status">Status of this document</h2>

index

@@ -99,11 +99,13 @@
   <h2 class="no-num no-toc" id=abstract>Abstract</h2>
 
   <p>This specification evolves HTML and its related APIs to ease the
-   authoring of Web-based applications. Additions include the context menus,
-   a direct-mode graphics canvas, inline popup windows, and server-sent
-   events. Heavy emphasis is placed on keeping the language backwards
-   compatible with existing legacy user agents and on keeping user agents
-   backwards compatible with existing legacy documents.
+   authoring of Web-based applications. Additions include context menus, a
+   direct-mode graphics canvas, a full duplex client-server communication
+   channel, more semantics, audio and video, various features for offline Web
+   applications, sandboxed iframes, and scoped styling. Heavy emphasis is
+   placed on keeping the language backwards compatible with existing legacy
+   user agents and on keeping user agents backwards compatible with existing
+   legacy documents.
 
   <h2 class="no-num no-toc" id=status>Status of this document</h2>