[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/src/doc/devguide/tutorial/tutorial-part1.rst

 .. _tutorial:
 
 ######################################
 C++ Tutorial: Getting Started (Part 1)
 ######################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
@@ skipping 57 matching lines @@
 
   $ cd pepper_$(VERSION)/getting_started
   $ make serve
 
 .. Note::
   :class: note
 
   The SDK may consist of several "bundles", one per Chrome/Pepper version (see
   :doc:`versioning information </version>`). In the sample invocation above
   ``pepper_$(VERSION)`` refers to the specific version you want to use. For
-  example, ``pepper_31``. If you don't know which version you need, use the
+  example, ``pepper_37``. If you don't know which version you need, use the
   one labeled ``(stable)`` by the ``naclsdk list`` command. See 
   :doc:`Download the Native Client SDK </sdk/download>` for more details.
 
 If no port number is specified, the server defaults to port 5103, and can be
 accessed at ``http://localhost:5103``.
 
 Any server can be used for the purpose of development. The one provided with the
 SDK is just a convenience, not a requirement.
 
 .. _tutorial_step_3:
 
 Step 3: Set up the Chrome browser
 =================================
 
-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's also
-important to use a Chrome version that's the same or newer than the SDK bundle
-used to build the Native Client modules.
+PNaCl is enabled by default in Chrome. You must use a version of Chrome that's

[Sam Clegg, 2014/10/08 17:38:01]

I wouldn't say this is a must.  How about "it is recommended that you use".

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

We could explain why it's recommended: older pexes will always work, but newer
pexes won't if they use APIs that were added to an SDK version newer than the
Chrome version used.

[jpmedley, 2014/11/05 03:56:11]

Done.

[jpmedley, 2014/11/05 03:56:11]

Done.

[jpmedley, 2014/11/05 03:56:11]

Done.

+the same or newer than the SDK bundle used to build Native Client modules.
 
 .. Note::
   :class: note
 
   To find out the version of Chrome, type ``about:chrome`` in the address bar.
 
 For a better development experience, it'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.
@@ skipping 183 matching lines @@
   applications and using the Pepper APIs.
 * See the :doc:`Building </devguide/devcycle/building>`, :doc:`Running
   </devguide/devcycle/running>`, and :doc:`Debugging pages
   </devguide/devcycle/debugging>` for information about how to build, run, and
   debug Native Client applications.
 * Check the `naclports <http://code.google.com/p/naclports/>`_ 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 `How to check code into naclports
   <http://code.google.com/p/naclports/wiki/HowTo_Checkin>`_).