[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/doc_generated/devguide/tutorial/tutorial-part1.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="c-tutorial-getting-started-part-1">
 <span id="tutorial"></span><h1 id="c-tutorial-getting-started-part-1"><span id="tutorial"></span>C++ Tutorial: Getting Started (Part 1)</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#overview" id="id1">Overview</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#what-the-application-in-this-tutorial-does" id="id2">What the application in this tutorial does</a></li>
 <li><a class="reference internal" href="#communication-between-javascript-and-native-client-modules" id="id3">Communication between JavaScript and Native Client modules</a></li>
@@ skipping 46 matching lines @@
 can be used to serve the application on <code>localhost</code>. A convenience Makefile
 rule called <code>serve</code> is the easiest way to invoke it:</p>
 <pre>
 $ cd pepper_$(VERSION)/getting_started
 $ make serve
 </pre>
 <aside class="note">
 The SDK may consist of several &#8220;bundles&#8221;, one per Chrome/Pepper version (see
 <a class="reference internal" href="/native-client/version.html"><em>versioning information</em></a>). In the sample invocation above
 <code>pepper_$(VERSION)</code> refers to the specific version you want to use. For
-example, <code>pepper_31</code>. If you don&#8217;t know which version you need, use the
+example, <code>pepper_37</code>. If you don&#8217;t know which version you need, use the
 one labeled <code>(stable)</code> by the <code>naclsdk list</code> command. See
 <a class="reference internal" href="/native-client/sdk/download.html"><em>Download the Native Client SDK</em></a> for more details.
 </aside>
 <p>If no port number is specified, the server defaults to port 5103, and can be
 accessed at <code>http://localhost:5103</code>.</p>
 <p>Any server can be used for the purpose of development. The one provided with the
 SDK is just a convenience, not a requirement.</p>
 <h2 id="step-3-set-up-the-chrome-browser"><span id="tutorial-step-3"></span>Step 3: Set up the Chrome browser</h2>
-<p>PNaCl is enabled by default in Chrome version 31 and later. Please make sure
-that you have a suitable version to work through this tutorial. It&#8217;s also
-important to use a Chrome version that&#8217;s the same or newer than the SDK bundle
-used to build the Native Client modules.</p>
+<p>PNaCl is enabled by default in Chrome. We recommend that you use a version of
+Chrome that&#8217;s the same or newer than the SDK bundle used to build Native Client
+modules. Older PNaCl modules will always work with newer versions of Chrome, but
+the converse is not true.</p>
 <aside class="note">
 To find out the version of Chrome, type <code>about:chrome</code> in the address bar.
 </aside>
 <p>For a better development experience, it&#8217;s also recommended to disable the
 Chrome cache. Chrome caches resources aggressively; disabling the cache helps
 make sure that the latest version of the Native Client module is loaded during
 development.</p>
 <ul class="small-gap">
 <li>Open Chrome&#8217;s developer tools by clicking the menu icon <img alt="menu-icon" src="/native-client/images/menu-icon.png" /> and
 choosing <code>Tools &gt; Developer tools</code>.</li>
@@ skipping 141 matching lines @@
 <li>See the <a class="reference internal" href="/native-client/devguide/devcycle/building.html"><em>Building</em></a>, <a class="reference internal" href="/native-client/devguide/devcycle/running.html"><em>Running</em></a>, and <a class="reference internal" href="/native-client/devguide/devcycle/debugging.html"><em>Debugging pages</em></a> for information about how to build, run, and
 debug Native Client applications.</li>
 <li>Check the <a class="reference external" href="http://code.google.com/p/naclports/">naclports</a> project to see
 what libraries have been ported for use with Native Client. If you port an
 open-source library for your own use, we recommend adding it to naclports
 (see <a class="reference external" href="http://code.google.com/p/naclports/wiki/HowTo_Checkin">How to check code into naclports</a>).</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}