[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/doc_generated/devguide/devcycle/running.html

Index: native_client_sdk/doc_generated/devguide/devcycle/running.html
diff --git a/native_client_sdk/doc_generated/devguide/devcycle/running.html b/native_client_sdk/doc_generated/devguide/devcycle/running.html
index 0cae390f4518e99f0c88f702464e418c7d195ba9..a03f7f9e832ec270b61c38a343fa3774034d92b5 100644
--- a/native_client_sdk/doc_generated/devguide/devcycle/running.html
+++ b/native_client_sdk/doc_generated/devguide/devcycle/running.html
@@ -158,8 +158,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
-<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
@@ -329,7 +329,7 @@ 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