[DOCS] Edit references to Chrome 31 and earlier.

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

Index: native_client_sdk/src/doc/devguide/devcycle/running.rst
diff --git a/native_client_sdk/src/doc/devguide/devcycle/running.rst b/native_client_sdk/src/doc/devguide/devcycle/running.rst
index 33944947330d92bcd001109cf99e34768da13b81..792b323b73b5a97da2376f5f4c3271fb18ee1097 100644
--- a/native_client_sdk/src/doc/devguide/devcycle/running.rst
+++ b/native_client_sdk/src/doc/devguide/devcycle/running.rst
@@ -146,8 +146,8 @@ 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:
@@ -364,7 +364,7 @@ extension:
    * 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.