[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/doc_generated/nacl-and-pnacl.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="nacl-and-pnacl">
 <span id="id1"></span><h1 id="nacl-and-pnacl"><span id="id1"></span>NaCl and PNaCl</h1>
 <p>This document describes the differences between <strong>Native Client</strong> and
 <strong>Portable Native Client</strong>, and provides recommendations for when to use each.</p>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#native-client-nacl" id="id6">Native Client (NaCl)</a></li>
 <li><a class="reference internal" href="#portable-native-client-pnacl" id="id7">Portable Native Client (PNaCl)</a></li>
@@ skipping 44 matching lines @@
 application. It does not have to be distributed through the Chrome Web Store. In
 short, PNaCl combines the portability of existing web technologies with the
 performance and security benefits of Native Client.</p>
 <p>PNaCl is a new technology, and as such it still has a few limitations
 as compared to NaCl. These limitations are described below.</p>
 <h2 id="when-to-use-pnacl"><span id="id4"></span>When to use PNaCl</h2>
 <p>PNaCl is the preferred toolchain for Native Client, and the only way to deploy
 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
 Web Store, and thereby take advantage of the conveniences of PNaCl, such as not
 having to explicitly compile your application for all supported architectures.</p>
 <h2 id="when-to-use-nacl"><span id="id5"></span>When to use NaCl</h2>
 <p>Use NaCl if any of the following apply to your application:</p>
 <ul class="small-gap">
 <li>Your application requires architecture-specific instructions such as, for
 example, inline assembly. PNaCl tries to offer high-performance portable
 equivalents. One such example is PNaCl&#8217;s <a class="reference internal" href="/native-client/reference/pnacl-c-cpp-language-support.html#portable-simd-vectors"><em>Portable SIMD Vectors</em></a>.</li>
 <li>Your application uses dynamic linking. PNaCl only supports static linking
 with a PNaCl port of the <code>newlib</code> C standard library. Dynamic linking and
 <code>glibc</code> are not yet supported in PNaCl. Work is under way to enable dynamic
 linking in future versions of PNaCl.</li>
 <li>Your application uses certain GNU extensions not supported by PNaCl&#8217;s LLVM
 toolchain, like taking the address of a label for computed <code>goto</code>, or nested
 functions.</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}