hixie: More editorial tweaks to the updated history section. (whatwg r3900)

hixie: More editorial tweaks to the updated history section. (whatwg
r3900)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3061&r2=1.3062&f=h
http://html5.org/tools/web-apps-tracker?from=3899&to=3900

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3061
retrieving revision 1.3062
diff -u -d -r1.3061 -r1.3062
--- Overview.html 18 Sep 2009 08:42:42 -0000 1.3061
+++ Overview.html 18 Sep 2009 08:51:36 -0000 1.3062
@@ -1252,7 +1252,7 @@
   3.2, which was completed in 1997. HTML4 followed, reaching
   completion in 1998.<p>At this time, the W3C membership decided to stop evolving HTML
   and instead begin work on an XML-based equivalent, called
-  XHTML. This effort started with a reforumlation of HTML4 in XML,
+  XHTML. This effort started with a reformulation of HTML4 in XML,
   known as XHTML 1.0, which added no new features except the new
   serialization, and which was completed in 2000. After XHTML 1.0, the
   W3C's focus turned to making it easier for other working groups to
@@ -1260,7 +1260,7 @@
   with this, the W3C also worked on a new language that was not
   compatible with the earlier HTML and XHTML languages, calling it
   XHTML2.<p>Around the time that HTML's evolution was stopped in 1998, parts
-  of the API for HTML developed by browsers were specified and
+  of the API for HTML developed by browser vendors were specified and
   published under the name DOM Level 1 (in 1998) and DOM Level 2 Core
   and DOM Level 2 HTML (starting in 2000 and culminating in
   2003). These efforts then petered out, with some DOM Level 3
@@ -1287,10 +1287,11 @@
   chosen direction for the Web's evolution; the W3C staff and
   membership voted to continue developing XML-based replacements
   instead.<p>Shortly thereafter, Apple, Mozilla, and Opera jointly announced
-  their intent to continue working on the effort. A public mailing
-  list was created, and the drafts were moved to the WHATWG site. The
-  copyright was subsequently amended to be jointly owned by all three
-  vendors, and to allow reuse of the specifications.<p>The WHATWG was based on several core principles, in particular
+  their intent to continue working on the effort under the umbrella of
+  a new venue called the WHATWG. A public mailing list was created,
+  and the draft was moved to the WHATWG site. The copyright was
+  subsequently amended to be jointly owned by all three vendors, and
+  to allow reuse of the specification.<p>The WHATWG was based on several core principles, in particular
   that technologies need to be backwards compatible, that
   specifications and implementations need to match even if this means
   changing the specification rather than the implementations, and that
@@ -1300,7 +1301,7 @@
   the HTML5 specification include what had previously been specified
   in three separate documents: HTML4, XHTML1, and DOM2 HTML. It also
   meant including significantly more detail than had previously been
-  included.<p>In 2006, the W3C indicated an interest to participate in the
+  considered the norm.<p>In 2006, the W3C indicated an interest to participate in the
   development of HTML5 after all, and in 2007 formed a working group
   chartered to work with the WHATWG on the development of the HTML5
   specification. Apple, Mozilla, and Opera allowed the W3C to publish

Received on Friday, 18 September 2009 08:52:32 UTC