[e] (0) Nothing particular about it, it could indeed apply to other t…

…hings... Fixing http://www.w3.org/Bugs/Public/show_bug.cgi?id=8084 git-svn-id: http://svn.whatwg.org/webapps@4366 340c8d12-0b0e-0410-8428-c7bf67bfef74
whatwg · Oct 27, 2009 · 10ce3df · 10ce3df
1 parent 9b566d6
commit 10ce3df
Show file tree

Hide file tree

Showing 3 changed files with 3 additions and 3 deletions.
diff --git a/complete.html b/complete.html
@@ -11903,7 +11903,7 @@ <h5 id=charset><span class=secno>4.2.5.5 </span>Specifying the document's charac
   the label used to declare the encoding, or does not use the same
   mechanism to detect the encoding of unlabelled content as another
   user agent) might end up interpreting technically benign plain text
-  content as HTML tags and JavaScript. In particular, this applies to
+  content as HTML tags and JavaScript. For example, this applies to
   encodings in which the bytes corresponding to "<code title="">&lt;script&gt;</code>" in ASCII can encode a different
   string. Authors should not use such encodings, which are known to
   include JIS_C6226-1983<!-- aka JIS-X-0208, x-JIS0208 -->,

diff --git a/index b/index
@@ -11721,7 +11721,7 @@ people expect to have work and what is necessary.
   the label used to declare the encoding, or does not use the same
   mechanism to detect the encoding of unlabelled content as another
   user agent) might end up interpreting technically benign plain text
-  content as HTML tags and JavaScript. In particular, this applies to
+  content as HTML tags and JavaScript. For example, this applies to
   encodings in which the bytes corresponding to "<code title="">&lt;script&gt;</code>" in ASCII can encode a different
   string. Authors should not use such encodings, which are known to
   include JIS_C6226-1983<!-- aka JIS-X-0208, x-JIS0208 -->,

diff --git a/source b/source
@@ -12389,7 +12389,7 @@ people expect to have work and what is necessary.
   the label used to declare the encoding, or does not use the same
   mechanism to detect the encoding of unlabelled content as another
   user agent) might end up interpreting technically benign plain text
-  content as HTML tags and JavaScript. In particular, this applies to
+  content as HTML tags and JavaScript. For example, this applies to
   encodings in which the bytes corresponding to "<code
   title="">&lt;script></code>" in ASCII can encode a different
   string. Authors should not use such encodings, which are known to