--- a/rdf-turtle/index.html	Wed Jun 20 14:26:08 2012 -0700
+++ b/rdf-turtle/index.html	Wed Jun 20 14:35:53 2012 -0700
@@ -964,7 +964,7 @@
         <p>Turtle content should be placed in a <code>script</code> tag with the 
         <code>type</code> attribute set to <code>text/turtle</code>. <code>&lt;</code> and <code>&gt;</code> symbols
         do not need to be escaped inside of script tags. The character encoding of the embedded Turtle
-        MUST match the HTML documents encoding.</p>
+        will match the HTML documents encoding.</p>
         <section class="informative">
           <h3>XHTML</h3>
           <p>
@@ -979,25 +979,18 @@
 <strong># ]]></strong>
 &lt;/script>
         </pre>
-          <p>When embedded in XHTML Turtle data blocks MUST be enclosed in CDATA sections. Those CDATA markers MUST be in Turtle comments. If the character sequence "<code>]]></code>" occurs in the document it MUST be escaped using strings escapes (<code>\u005d\u0054\u003e</code>). This will also make Turtle safe in polyglot documents served as both <code>text/html</code>
-          and <code>application/xhtml+xml</code>.</p>
+          <p>When embedded in XHTML Turtle data blocks must be enclosed in CDATA sections. Those CDATA markers must be in Turtle comments. If the character sequence "<code>]]></code>" occurs in the document it must be escaped using strings escapes (<code>\u005d\u0054\u003e</code>). This will also make Turtle safe in polyglot documents served as both <code>text/html</code>
+          and <code>application/xhtml+xml</code>. Failing to use CDATA sections or escape "<code>]]></code>" may result in a non well-formed XML document.</p>
         </section>
         <section id="in-html-parsing" class="informative">
           <h3>Parsing Turtle in HTML</h3>
           <p>There are no syntactic or grammar differences between parsing Turtle that has been embedded 
           and normal Turtle documents. Each <code>script</code> data block is considered to be it's own 
-          Turtle document. <code>@prefix</code>, <code>@base</code> declarations MUST NOT effect other
-          data blocks. All Turtle data blocks in a HTML document share the same document base URI as the HTML 
-          document. The HTML <code>lang</code> attribute or XHTML <code>xml:lang</code> attribute have
-          no effect on the parsing of the data blocks.</p>
-
-          <p class="issue">
-The <a href="http://media02.hongkiat.com/error_404_01/turbomilk.jpg">unescaped character data</a> within a <code>script</code> data block with <code>type</code> <code>text/turtle</code> is a Turtle document.
-While documents with media type <code>text/turtle</code> use the UTF-8 character encoding, the character encoding of HTML documents containing Turtle data blocs MAY use other encodings, provided that characters in those data blocks correspond to unicode code points in the <a href="#sec-grammar-grammar">Turtle grammar</a>.
-<code>@prefix</code> and <code>@base</code> declarations in a Turtle data bloc are scoped to that data block and MUST NOT effect other data blocks.
+          Turtle document. <code>@prefix</code> and <code>@base</code> declarations in a Turtle data bloc are scoped to that data block and do not effect other data blocks.
 The HTML <code>lang</code> attribute or XHTML <code>xml:lang</code> attribute have no effect on the parsing of the data blocks.
 The base URI of the encapsulating HTML document provides a "Base URI Embedded in Content" per RFC3986 section 5.1.1.
-	  </p>
+
+
         </section>
       </section>      
       <section id="sec-mediaReg" class="appendix">