CVS html5/html-xhtml-author-guide

Update of /sources/public/html5/html-xhtml-author-guide
In directory roscoe:/tmp/cvs-serv16006/html-xhtml-author-guide

Modified Files:
	html-xhtml-authoring-guide.html 
Log Message:
Typo

--- /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html	2013/09/02 04:30:30	1.129
+++ /sources/public/html5/html-xhtml-author-guide/html-xhtml-authoring-guide.html	2013/09/02 04:32:46	1.130
@@ -132,10 +132,10 @@
         denominator would have required.</p>
 
     <p> For instance, included in the set of constraints on the serialization is the requirement to use the UTF-8 encoding.
-        This requirement is not only because of the
-        documented benefits (the HTML-specific ones are described in HTML5 [[!HTML5]]) of this encoding - which in turn has lead the HTML5 specification to recommend
+        This requirement is not only because of the documented benefits (the HTML-specific benefits are described in HTML5 [[!HTML5]]) –
+        which in turn has lead the HTML5 specification to recommend
         that all new documents use UTF-8, but also because it is the sole encoding that <em>every</em> parser, be it an HTML parser or
-        an XML parser, is required to support. Also,  UTF-8 might in some situatiosn be the sole <em>HTML-conforming</em> option, since it is one of
+        an XML parser, is required to support. Also,  UTF-8 might in some situations be the sole <em>HTML-conforming</em> option, since it is one of
         only two encodings (the other being UTF-16, with its own, separate set of well-known issues) for which XML well-formed
         rules doesn’t require the encoding to be explicitly declared. This in turn has the benefit that the anyhow HTML-invalid XML
         encoding declaration kan reliably be skipped without causing any side-effects. E.g. if one opted to use the <code>KOI8-R</code>,

Received on Monday, 2 September 2013 04:32:47 UTC