typo markup fix; make abortion legal for browsers

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

index

@@ -13190,13 +13190,11 @@ interface <dfn id="storageitem">StorageItem</dfn> {
    it was registering the "Cuddly Bear Happy Content Handler". User agents
    should therefore use the handler's domain in any UI along with any title.
 
-  <p><strong>Hostile handler metadata.</strong>
-
-  <p> User agents should protect against typical attacks against strings
-   embedded in their interface, for example ensuring that markup or escape
-   characters in such strings are not executed, that null bytes are properly
-   handled, that over-long strings do not cause crashes or buffer overruns,
-   and so forth.
+  <p><strong>Hostile handler metadata.</strong> User agents should protect
+   against typical attacks against strings embedded in their interface, for
+   example ensuring that markup or escape characters in such strings are not
+   executed, that null bytes are properly handled, that over-long strings do
+   not cause crashes or buffer overruns, and so forth.
 
   <h3 id="scs-alternate"><span class="secno">4.11. </span><span
    title="SCS"><a href="#scs">[SCS]</a></span> Alternate style sheets: the
@@ -18244,8 +18242,10 @@ function receiver(e) {
   <p>This specification defines the parsing rules for HTML documents, whether
    they are syntactically valid or not. Certain points in the parsing
    algorithm are said to be <dfn id="parse" title="parse error">parse
-   errors</dfn>. The error handling for parse errors is well-defined, and
-   user agents must act as described below when encountering such problems.
+   errors</dfn>. The error handling for parse errors is well-defined: user
+   agents must either act as described below when encountering such problems,
+   or must abort processing at the first error that they encounter for which
+   they do not wish to apply the rules described below.
 
   <p>Conformance checkers must report at least one parse error condition to
    the user if one or more parse error conditions exist in the document and

source

@@ -11378,7 +11378,7 @@ interface <dfn>StorageItem</dfn> {
   Handler". User agents should therefore use the handler's domain in
   any UI along with any title.</p>
 
-  <p><strong>Hostile handler metadata.</strong></p> User agents should
+  <p><strong>Hostile handler metadata.</strong> User agents should
   protect against typical attacks against strings embedded in their
   interface, for example ensuring that markup or escape characters in
   such strings are not executed, that null bytes are properly handled,
@@ -16249,9 +16249,11 @@ function receiver(e) {
   <p>This specification defines the parsing rules for HTML documents,
   whether they are syntactically valid or not. Certain points in the
   parsing algorithm are said to be <dfn title="parse error">parse
-  errors</dfn>. The error handling for parse errors is well-defined,
-  and user agents must act as described below when encountering such
-  problems.</p>
+  errors</dfn>. The error handling for parse errors is well-defined:
+  user agents must either act as described below when encountering
+  such problems, or must abort processing at the first error that they
+  encounter for which they do not wish to apply the rules described
+  below.</p>
 
   <p>Conformance checkers must report at least one parse error
   condition to the user if one or more parse error conditions exist in