Update references to the extension gallery.

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

 <div id="pageData-name" class="pageData">Packaging</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
 <p>
 This page describes how to package your extension.
 As the <a href="overview.html">Overview</a> explains,
 extensions are packaged as signed ZIP files
-with the file extension "crx" &mdash;
-for example, <code>myextension.crx</code>.
+with the file extension "crx"&mdash;for example,
+<code>myextension.crx</code>.
 </p>
 
 <p>
 <b>Note:</b>
 You might not need to package your extension.
 If you publish your extension using the
 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a>,
 then the only reason to create your own <code>.crx</code> file
-would be to distribute a non-public version &mdash;
-for example, to alpha testers.
+would be to distribute a non-public version&mdash;for example,
+to alpha testers.
+You can find information on publishing extensions and apps in the
+Chrome Web Store getting started tutorial, starting at
+<a href="http://code.google.com/chrome/webstore/docs/get_started_simple.html#step5">Step 5: Zip up your app</a>.
 </p>
 
-<!-- [PENDING: Refer to instructions on submitting an extension for inclusion in the gallery.] -->
-
 <p>
 When you package an extension,
 the extension is assigned a unique key pair.
 The extension's ID is based on a hash of the public key.
 The private key is kept private
 and used to sign each version of the extension.
 </p>
 
 
 <h2>Creating a package</h2>
@@ skipping 13 matching lines @@
     click the +.
   </li>
 
   <li>
     Click the <b>Pack extension</b> button.
     A dialog appears.
   </li>
 
   <li>
     In the <b>Extension root directory</b> field,
-    specify the path to the extension's folder &mdash;
-    for example, <code>c:\myext</code>.
+    specify the path to the extension's folder&mdash;for example,
+    <code>c:\myext</code>.
     (Ignore the other field;
     you don't specify a private key file
     the first time you package a particular extension.)
   </li>
 
   <li>
     Click <b>OK</b>.
     The packager creates two files:
     a <code>.crx</code> file,
     which is the actual extension that can be installed,
@@ skipping 37 matching lines @@
     by going to this URL: <b>chrome://extensions</b>
   </li>
 
   <li>
     Click the <b>Pack extension</b> button.
     A dialog appears.
   </li>
 
   <li>
     In the <b>Extension root directory</b> field,
-    specify the path to the extension's folder &mdash;
-    for example, <code>c:\myext</code>.
+    specify the path to the extension's folder&mdash;for example,
+    <code>c:\myext</code>.
   </li>
 
   <li>
     In the <b>Private key file</b> field,
     specify the location of the
-    already generated <code>.pem</code> file for this extension &mdash;
-    for example, <code>c:\myext.pem</code>.
+    already generated <code>.pem</code> file for this extension&mdash;for
+    example, <code>c:\myext.pem</code>.
   </li>
 
   <li>
     Click <b>OK</b>.
   </li>
 </ol>
 
 <p>If the updated extension is successfully packaged, you'll see a dialog like this:</p>
 
 <img src="images/update-success.gif"
@@ skipping 18 matching lines @@
 <p>
 To suppress the dialog,
 add <code>--no-message-box</code> to the command.
 </p>
 
 <h2>Package format and scripts</h2>
 <p>
 For more information on the format, as well as pointers to scripts you can use
 to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a>.
 </p>