[e] (0) remove paragraph since it has many problems and it's not clea…

…r what it was supposed to mean

Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=12484

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

complete.html

@@ -3407,11 +3407,6 @@ <h4 id=conformance-classes><span class=secno>2.2.1 </span>Conformance classes</h
   would imply that documents are not allowed to contain elements named
   <code title="">foobar</code>.</p>
 
-<!-- The following paragraph is not included in the WHATWG copy
-because it is wrong. For example, content models are not syntax. It's
-also unnecessary. What kinds of things are conformance requirements is
-explained in the previous section, which talks about RFC 2119. -->
-
   <p class="note impl">There is no implied relationship between
   document conformance requirements and implementation conformance
   requirements. User agents are not free to handle non-conformant

index

@@ -3304,11 +3304,6 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   would imply that documents are not allowed to contain elements named
   <code title="">foobar</code>.</p>
 
-<!-- The following paragraph is not included in the WHATWG copy
-because it is wrong. For example, content models are not syntax. It's
-also unnecessary. What kinds of things are conformance requirements is
-explained in the previous section, which talks about RFC 2119. -->
-
   <p class="note impl">There is no implied relationship between
   document conformance requirements and implementation conformance
   requirements. User agents are not free to handle non-conformant

source

@@ -2276,18 +2276,6 @@ a.setAttribute('href', 'http://example.com/'); // change the content attribute d
   would imply that documents are not allowed to contain elements named
   <code title="">foobar</code>.</p>
 
-<!-- The following paragraph is not included in the WHATWG copy
-because it is wrong. For example, content models are not syntax. It's
-also unnecessary. What kinds of things are conformance requirements is
-explained in the previous section, which talks about RFC 2119. -->
-<!--END html--><!--END dev-html--><!--END complete--><!--END epub--><!--CONFORMANCE--><!--FORK-->
-  <p class="note">the conformance requirements for documents include
-  syntax (the &lt;table> element is conforming as a child of
-  &lt;body>, but not as a child ot &lt;title>), and semantics (the
-  &lt;table> elements denotes a multi-dimensional data table, not a
-  piece of furniture).</p>
-<!--START html--><!--START dev-html--><!--START complete--><!--START epub--><!--CONFORMANCE--><!--FORK-->
-
   <p class="note impl">There is no implied relationship between
   document conformance requirements and implementation conformance
   requirements. User agents are not free to handle non-conformant