[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/doc_generated/nacl-and-pnacl.html

Index: native_client_sdk/doc_generated/nacl-and-pnacl.html
diff --git a/native_client_sdk/doc_generated/nacl-and-pnacl.html b/native_client_sdk/doc_generated/nacl-and-pnacl.html
index b884cc78ae2e705f5d21315fd7177c5305c58644..f88487cb98152298e97b90bcf9d6ec1daa95bfdf 100644
--- a/native_client_sdk/doc_generated/nacl-and-pnacl.html
+++ b/native_client_sdk/doc_generated/nacl-and-pnacl.html
@@ -62,11 +62,11 @@ as compared to NaCl. These limitations are described below.</p>
 Native Client modules without the Google Web Store. Unless your project is
 subject to one of the narrow limitations described under &#8220;<a class="reference internal" href="#when-to-use-nacl"><em>When to use
 NaCl</em></a>&#8221;, you should use PNaCl.</p>
-<p>Since version 31, Chrome supports translation of pexe
-modules and their use in web applications without requiring installation either
-of a browser plug-in or of the applications themselves. Native Client and PNaCl
-are open-source technologies, and our hope is that they will be added to other
-hosting platforms in the future.</p>
+<p>Chrome supports translation of pexe modules and their use in web applications
+without requiring installation either of a browser plug-in or of the
+applications themselves. Native Client and PNaCl are open-source technologies,
+and our hope is that they will be added to other hosting platforms in the
+future.</p>
 <p>If controlled distribution through the Chrome Web Store is an important part of
 your product plan, the benefits of PNaCl are less critical for you. But you can
 still use the PNaCl toolchain and distribute your application through the Chrome