Fix a lot of support links.

native_client_sdk/doc_generated/devguide/coding/3D-graphics.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="d-graphics">
 <span id="devguide-coding-3d-graphics"></span><h1 id="d-graphics"><span id="devguide-coding-3d-graphics"></span>3D Graphics</h1>
 <p>Native Client applications use the <a class="reference external" href="http://en.wikipedia.org/wiki/OpenGL_ES">OpenGL ES 2.0</a> API for 3D rendering. This document
 describes how to call the OpenGL ES 2.0 interface in a Native Client module and
 how to build an efficient rendering loop. It also explains how to validate GPU
 drivers and test for specific GPU capabilities, and provides tips to help ensure
 your rendering code runs efficiently.</p>
 <aside class="note">
@@ skipping 102 matching lines @@
 been disabled.&#8221;</p>
 <p>The manifest-based check applies only to downloads directly from the Chrome Web
 Store. It is not performed when an application is loaded via <a class="reference external" href="/webstore/inline_installation">inline
 installation</a>.</p>
 <h3 id="what-to-do-when-there-are-problems">What to do when there are problems</h3>
 <p>Using the vetting procedure described above, you should be able to detect the
 most common problems before your application runs. If there are problems, your
 code should describe the issue as clearly as possible. That&#8217;s easy if there is a
 missing feature. Failure to create a graphics context is tougher to diagnose. At
 the very least, you can suggest that the user try to update the driver.  You
-might want to linke to the Chrome page that describes <a class="reference external" href="http://support.google.com/chrome/bin/answer.py?hl=en&amp;answer=1202946">how to do updates</a>.</p>
+might want to linke to the Chrome page that describes <a class="reference external" href="https://support.google.com/chrome/answer/1202946">how to do updates</a>.</p>
 <p>If a user can&#8217;t update the driver, or their problem persists, be sure to gather
 information about their graphics environment. Ask for the contents of the Chrome
 <code>about:gpu</code> page.</p>
 <h3 id="document-unreliable-drivers">Document unreliable drivers</h3>
 <p>It can be helpful to include information about known dubious drivers in your
 user documentation. This might help identify if a rogue driver is the cause of a
 problem. There are many sources of GPU driver blacklists. Two such lists can be
 found at the <a class="reference external" href="http://src.chromium.org/viewvc/chrome/trunk/deps/gpu/software_rendering_list/software_rendering_list.json">Chromium project</a>
 and <a class="reference external" href="http://www.khronos.org/webgl/wiki/BlacklistsAndWhitelists">Khronos</a>. You
 can use these lists to include information in your documentation that warns
@@ skipping 274 matching lines @@
 2.0 implementation when you update a portion of a buffer (with
 <code>glSubBufferData</code> for example) the entire buffer must be reprocessed. To
 avoid this problem, keep static and dynamic data in different buffers.</li>
 <li><strong>Don&#8217;t call glDisable(GL_TEXTURE_2D).</strong> This is an OpenGL ES 2.0
 error. Each time it is called, an error messages will appear in Chrome&#8217;s
 <code>about:gpu</code> tab.</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_article}}