hixie: use more consistent wording (this is referred to as migration in other parts of the spec) (whatwg r4928)

hixie: use more consistent wording (this is referred to as migration in
other parts of the spec) (whatwg r4928)

http://dev.w3.org/cvsweb/html5/spec/Overview.html?r1=1.3948&r2=1.3949&f=h
http://html5.org/tools/web-apps-tracker?from=4927&to=4928

===================================================================
RCS file: /sources/public/html5/spec/Overview.html,v
retrieving revision 1.3948
retrieving revision 1.3949
diff -u -d -r1.3948 -r1.3949
--- Overview.html 31 Mar 2010 20:42:28 -0000 1.3948
+++ Overview.html 31 Mar 2010 21:02:02 -0000 1.3949
@@ -1992,17 +1992,18 @@
    </dd>
 
 
-   <dt>Errors that are intended to help authors of polyglot documents</dt>
+   <dt>Errors that are intended to help authors migrating to and from XHTML</dt>
 
    <dd>
 
     <p>Some authors like to write files that can be interpreted as
-    both XML and HTML with similar results. These are known as
-    polyglot documents. Though this practice is discouraged in general
-    due to the myriad of subtle complications involved (especially
-    when involving scripting, styling, or any kind of automated
-    serialization), this specification has a few restrictions intended
-    to at least somewhat mitigate the difficulties.</p>
+    both XML and HTML with similar results. Though this practice is
+    discouraged in general due to the myriad of subtle complications
+    involved (especially when involving scripting, styling, or any
+    kind of automated serialization), this specification has a few
+    restrictions intended to at least somewhat mitigate the
+    difficulties. This makes it easier for authors to use this as a
+    transitionary step when migrating between HTML and XHTML.</p>
 
     <p class="example">For example, there are somewhat complicated
     rules surrounding the <code title="attr-lang"><a href="#attr-lang">lang</a></code> and
@@ -2012,8 +2013,8 @@
     <p class="example">Another example would be the restrictions on
     the values of <code title="">xmlns</code> attributes in the HTML
     serialization, which are intended to ensure that elements in
-    conforming polyglot documents end up in the same namespaces
-    whether processed as HTML or XML.</p>
+    conforming documents end up in the same namespaces whether
+    processed as HTML or XML.</p>
 
    </dd>

Received on Thursday, 1 April 2010 05:45:56 UTC