[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/doc_generated/devguide/devcycle/running.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="running">
 <span id="devcycle-running"></span><h1 id="running"><span id="devcycle-running"></span>Running</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#introduction" id="id5">Introduction</a></li>
 <li><a class="reference internal" href="#portable-native-client-pnacl-applications" id="id6">Portable Native Client (PNaCl) applications</a></li>
 <li><a class="reference internal" href="#native-client-applications-and-the-chrome-web-store" id="id7">Native Client applications and the Chrome Web Store</a></li>
 <li><p class="first"><a class="reference internal" href="#prerequisites" id="id8">Prerequisites</a></p>
@@ skipping 140 matching lines @@
 listed in the table above (NaCl flag, web server, and CWS metadata). The
 subsequent sections of the document provide instructions for how to use each of
 the four techniques.</p>
 <h2 id="prerequisites">Prerequisites</h2>
 <h3 id="browser-and-pepper-versions">Browser and Pepper versions</h3>
 <p>Before you run a new build of your application, make sure that you&#8217;re using the
 correct version of Chrome. Each version of Chrome supports a corresponding
 version of the Pepper API. You (and your users) must use a version of Chrome
 that is equal to or higher than the version of the Pepper API that your
 application uses. For example, if you compiled your application using the
-<code>pepper_31</code> bundle, your application uses the Pepper 31 API, and you must run
-the application in Chrome 31 or higher. To check which version of Chrome you&#8217;re
+<code>pepper_37</code> bundle, your application uses the Pepper 37 API, and you must run
+the application in Chrome 37 or higher. To check which version of Chrome you&#8217;re
 using, type <code>about:version</code> in the Chrome address bar.</p>
 <h3 id="chrome-cache"><span id="cache"></span>Chrome Cache</h3>
 <p>Chrome caches resources aggressively. You should disable Chrome&#8217;s cache whenever
 you are developing a Native Client application in order to make sure Chrome
 loads new versions of your application. Follow the instructions <a class="reference internal" href="/native-client/devguide/tutorial/tutorial-part1.html#tutorial-step-3"><em>in the
 tutorial</em></a>.</p>
 <h2 id="requirements"><span id="id1"></span>Requirements</h2>
 <h3 id="native-client-flag"><span id="flag"></span>Native Client flag</h3>
 <p>Native Client is automatically enabled for applications that are installed from
 the Chrome Web Store. To enable Native Client for applications that are not
@@ skipping 149 matching lines @@
 <li>Start a web server to serve your application.<ul class="small-gap">
 <li>You can use the <a class="reference internal" href="#web-server"><em>local web server</em></a> included with the
 Native Client SDK if you want.</li>
 </ul>
 </li>
 <li>Upload your application (.html, .nmf, .nexe, .css, .js, image files, etc.)
 to the server.<ul class="small-gap">
 <li>If you&#8217;re using the local server included with the Native Client SDK,
 simply put your application under the <code>examples</code> directory in the SDK
 bundle you are using (e.g., in the directory
-<code>pepper_31/examples/my_app</code>).</li>
+<code>pepper_37/examples/my_app</code>).</li>
 </ul>
 </li>
 <li>Create a Chrome Web Store manifest file and one or more icons for your
 application.<ul class="small-gap">
 <li>Follow the instructions above under <a class="reference internal" href="#metadata"><em>Chrome Web Store metadata</em></a> to create these files.</li>
 <li>In the CWS manifest file, the <code>web_url</code> field should specify the
 location of your application on your server. If you&#8217;re using the local
 server included with the SDK, the <code>web_url</code> field should look something
 like <code>http://localhost:5103/my_app/my_app_main_page.html</code>.</li>
 </ul>
@@ skipping 93 matching lines @@
 </ul>
 </li>
 </ol>
 <p>To publish an application to the world after publishing it to test accounts,
 you must first unpublish the application. For additional information see
 <a class="reference external" href="/webstore/docs/publish">Publishing Your App</a>, and in particular <a class="reference external" href="/webstore/publish#testaccounts">Publishing
 to test accounts</a>.</p>
 </section>
 
 {{/partials.standard_nacl_article}}