[DOCS] Edit references to Chrome 31 and earlier.

native_client_sdk/doc_generated/faq.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="frequently-asked-questions">
 <h1 id="frequently-asked-questions">Frequently Asked Questions</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#what-is-native-client-good-for" id="id1">What is Native Client Good For?</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#why-did-google-build-native-client" id="id2">Why did Google build Native Client?</a></li>
 <li><a class="reference internal" href="#when-should-i-use-portable-native-client-instead-of-native-client" id="id3">When should I use Portable Native Client instead of Native Client?</a></li>
@@ skipping 416 matching lines @@
 has access to the same per-application storage that JavaScript has via Local
 Storage). HTML5 File System can be used, among others. For POSIX compatabiliy
 the Native Client SDK includes a library called nacl_io which allows the
 application to interact with all these types of files via standard POSIX I/O
 functions (e.g. open/fopen/read/write/...). See <a class="reference internal" href="/native-client/devguide/coding/nacl_io.html"><em>Using NaCl I/O</em></a> for more details.</li>
 </ul>
 <h2 id="troubleshooting"><span id="faq-troubleshooting"></span>Troubleshooting</h2>
 <h3 id="my-pexe-isn-t-loading-help">My <code>.pexe</code> isn&#8217;t loading, help!</h3>
 <ul class="small-gap">
 <li>You must use Google Chrome version 31 or greater for Portable Native
-Client. Make sure you have Portable Native Client installed in
-<code>about:nacl</code>; if not open <code>about:components</code> and &#8220;Check for
-update&#8221; for PNaCl.</li>
-<li>PNaCl <code>.pexe</code> must be compiled with pepper_31 SDK or higher (earlier
-SDK versions had experimental support for PNaCl, now deprecated).</li>
+Client. Please <a class="reference external" href="http://www.google.com/chrome/">upgrade now</a> if you are
+not. If you&#8217;re already using a recent version,  open <code>about:components</code> and
+&#8220;Check for update&#8221; for PNaCl. Find your version of chrome by openning
+<code>about:chrome</code>.</li>
+<li>A PNaCl <code>.pexe</code> must be compiled with pepper_31 SDK or higher. <a class="reference internal" href="/native-client/sdk/download.html#updating-bundles"><em>Update
+your bundles</em></a> and make sure you&#8217;re using a version of
+Chrome that matches the SDK version.</li>
 <li>Your application can verify that Portable Native Client is supported
 in JavaScript with <code>navigator.mimeTypes['application/x-pnacl'] !==
 undefined</code>. This is preferred over checking the Chrome version.</li>
 </ul>
 <h3 id="my-nexe-files-never-finish-loading-what-gives">My <code>.nexe</code> files never finish loading. What gives?</h3>
 <p>Here are ways to resolve some common problems that can prevent loading:</p>
 <ul class="small-gap">
 <li>You must use Google Chrome version 14 or greater for Native Client.</li>
 <li>If you haven&#8217;t already done so, enable the Native Client flag in
 Google Chrome. Type <code>about:flags</code> in the Chrome address bar, scroll
@@ skipping 19 matching lines @@
 you&#8217;re loading the correct <code>.nexe</code> file by building a separate
 <code>.nexe</code> for each architecture, and using a <code>.nmf</code> manifest file to
 let the browser select the correct <code>.nexe</code> file. Note: the need to
 select a processor-specific <code>.nexe</code> goes away with Portable Native
 Client.</li>
 <li>If things still aren&#8217;t working, <a class="reference internal" href="/native-client/help.html"><em>ask for help</em></a>!</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}