Update references to the extension gallery.

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

 <div id="pageData-name" class="pageData">Hosting</div>
 
 <p>
 This page tells you how to host <code>.crx</code> files
 on your own server.
 If you distribute your extension, app, or theme solely through the
 <a href="http://chrome.google.com/webstore">Chrome Web Store</a>,
 you don't need this page.
-Instead, consult the store help and
+Instead, consult the
+<a href="http://www.google.com/support/chrome_webstore/">store help</a> and
 <a href="http://code.google.com/chrome/webstore/index.html">developer documentation</a>.
-<!-- PENDING: add a link to the help -->
-</p>
-
-<p class="note">
-<strong>Note:</strong>
-If you've already published extensions to the 
-<a href="https://chrome.google.com/extensions">Extensions Gallery</a>,
-they will be merged into the store.
 </p>
 
 <p>
 By convention, extensions,
 installable web apps, and themes are served&mdash;whether
 by the Chrome Web Store or by a custom server&mdash;as
 <code>.crx</code> files.
 When you upload a ZIP file with the
 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a>,
 the dashboard creates the <code>.crx</code> file for you.
@@ skipping 53 matching lines @@
 The most common reason for failing to recognize an installable file
 is that the server sends the header
 <code>X-Content-Type-Options: no sniff</code>.
 The second most common reason
 is that the server sends an unknown content type&mdash;one
 that isn't in the previous list.
 To fix an HTTP header issue,
 either change the configuration of the server
 or try hosting the <code>.crx</code> file at another server.
 </p>