[html5] r4928 - [e] (0) use more consistent wording (this is referred to as migration in other p [...]

[whatwg at whatwg.org]

Author: ianh
Date: 2010-03-31 14:01:55 -0700 (Wed, 31 Mar 2010)
New Revision: 4928

Modified:
   complete.html
   index
   source
Log:
[e] (0) use more consistent wording (this is referred to as migration in other parts of the spec)

Modified: complete.html
===================================================================
--- complete.html	2010-03-31 20:42:21 UTC (rev 4927)
+++ complete.html	2010-03-31 21:01:55 UTC (rev 4928)
@@ -2355,17 +2355,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
@@ -2375,8 +2376,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>
 

Modified: index
===================================================================
--- index	2010-03-31 20:42:21 UTC (rev 4927)
+++ index	2010-03-31 21:01:55 UTC (rev 4928)
@@ -2253,17 +2253,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
@@ -2273,8 +2274,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>
 

Modified: source
===================================================================
--- source	2010-03-31 20:42:21 UTC (rev 4927)
+++ source	2010-03-31 21:01:55 UTC (rev 4928)
@@ -1195,17 +1195,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">lang</code> and
@@ -1215,8 +1216,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>