[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/src/doc/devguide/devcycle/running.rst

 .. _devcycle-running:
 
 #######
 Running
 #######
 
 
 .. contents::
   :local:
   :backlinks: none
@@ skipping 128 matching lines @@
 =============
 
 Browser and Pepper versions
 ---------------------------
 
 Before you run a new build of your application, make sure that you'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
-``pepper_31`` 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're
+``pepper_37`` 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're

[JF, 2014/10/08 22:00:37]

Should we make this some form of a macro that translates to the latest version
at rst generation time? We can probably sync this with the release notes?

 using, type ``about:version`` in the Chrome address bar.
 
 .. _cache:
 
 Chrome Cache
 ------------
 
 Chrome caches resources aggressively. You should disable Chrome'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 :ref:`in the
@@ skipping 196 matching lines @@
 #. Start a web server to serve your application.
 
    * You can use the :ref:`local web server <web_server>` included with the
      Native Client SDK if you want.
 #. Upload your application (.html, .nmf, .nexe, .css, .js, image files, etc.)
    to the server.
 
    * If you're using the local server included with the Native Client SDK,
      simply put your application under the ``examples`` directory in the SDK
      bundle you are using (e.g., in the directory
-     ``pepper_31/examples/my_app``).
+     ``pepper_37/examples/my_app``).
 #. Create a Chrome Web Store manifest file and one or more icons for your
    application.
 
    * Follow the instructions above under :ref:`Chrome Web Store metadata
      <metadata>` to create these files.
    * In the CWS manifest file, the ``web_url`` field should specify the
      location of your application on your server. If you're using the local
      server included with the SDK, the ``web_url`` field should look something
      like ``http://localhost:5103/my_app/my_app_main_page.html``.
 #. Put the CWS manifest file and the application icon(s) in the same directory
@@ skipping 93 matching lines @@
      be able to find the application by searching in the CWS.
 
 To publish an application to the world after publishing it to test accounts,
 you must first unpublish the application. For additional information see
 `Publishing Your App </webstore/docs/publish>`_, and in particular `Publishing
 to test accounts </webstore/publish#testaccounts>`_.
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. |extensions| image:: /images/extensions-management.png
 .. |new-tab-apps| image:: /images/new-tab-apps.png