[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/src/doc/sdk/download.rst

 .. _download:
 
 Download the Native Client SDK
 ==============================
 
 This page provides an overview of the Native Client SDK, and instructions for
 downloading and installing the SDK.
 
 .. raw:: html
   
@@ skipping 156 matching lines @@
    The sample output above shows that several bundles are available for
    download, and that you have already installed the latest revision of the
    ``sdk_tools`` bundle, which was included in the zip file. You never need to
    update the ``sdk_tools`` bundle. It is updated automatically (if necessary)
    whenever you run ``naclsdk``.
    
    Bundles are labeled post-stable, stable, beta, dev, or canary. These labels
    usually correspond to the current versions of Chrome. We recommend that you
    develop against a "stable" bundle, because such bundles can be used by all
    current Chrome users. Native Client is designed to be backward-compatible.For
-   example, applications developed with the ``pepper_31`` bundle can run in
-   Chrome 31, Chrome 32, etc..
+   example, applications developed with the ``pepper_37`` bundle can run in
+   Chrome 37, Chrome 38, etc..
 
 #. Run ``naclsdk`` with the ``update`` command to download recommended bundles,
    including the current "stable" bundle.
 
    On Mac/Linux::
 
      $ ./naclsdk update
 
    On Windows::
 
@@ skipping 81 matching lines @@
 Next steps
 ----------
 
 * Browse the `Release Notes <release-notes>`_ for important
   information about the SDK and new bundles.
 * If you're just starting with Native Client, we recommend reading the 
   `Technical Overview <../overview>`_ and walking through the
   `Getting Started Tutorial <devguide/tutorial/tutorial-part1>`_.
 * If you'd rather dive in, see
   `Building Native Client Modules <devguide/devcycle/building>`_.