Update references to the extension gallery.

chrome/common/extensions/docs/static/npapi.html

 <div id="pageData-name" class="pageData">NPAPI Plugins</div>
 
 <p>
 Leveraging HTML and JavaScript
 makes developing new extensions really easy,
 but what if you have existing legacy or proprietary code
 that you want to reuse in your extension?
 You can bundle an NPAPI plugin with your extension,
 allowing you to call into native binary code from JavaScript.
 </p>
 
 <h2>Warning</h2>
 
 <p align="center"><b>NPAPI is a really big hammer that should only be used when no other approach will work.</b>
 
 <p>Code running in an NPAPI plugin has the full permissions of the current user and is not sandboxed or shielded from malicious input by Google Chrome in any way. You should be especially cautious when processing input from untrusted sources, such as when working with <a href="content_scripts.html#security-considerations">content scripts</a> or XMLHttpRequest.
 
 <p>Because of the additional security risks NPAPI poses to users, extensions that use it will require manual review before being accepted in the
-<a href="https://chrome.google.com/webstore">web store</a> or 
-<a href="https://chrome.google.com/extensions">extension gallery</a>.
+<a href="https://chrome.google.com/webstore">Chrome Web Store</a>.</p>
 
 <h2>Details</h2>
 
 <p>
 How to develop an NPAPI plugin is outside the scope of this document.
 See <a href="https://developer.mozilla.org/en/Plugins">Mozilla's
 NPAPI plugin reference</a> for information on how to do that.
 </p>
 
 <p>
@@ skipping 59 matching lines @@
 including an NPAPI plugin whenever possible.
 </p>
 
 <p>
 Marking your NPAPI plugin "public" increase the attack surface of your
 extension because the plugin is exposed directly to web content, making
 it easier for a malicious web site to manipulate your plugin.  Instead,
 avoid making your NPAPI plugin public whenever possible.
 </p>