Update references to the extension gallery.

chrome/common/extensions/docs/packaging.html

Index: chrome/common/extensions/docs/packaging.html
===================================================================
--- chrome/common/extensions/docs/packaging.html	(revision 98127)
+++ chrome/common/extensions/docs/packaging.html	(working copy)
@@ -340,8 +340,8 @@
 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" —
-for example, <code>myextension.crx</code>.
+with the file extension "crx"—for example,
+<code>myextension.crx</code>.
 </p>
 
 <p>
@@ -350,12 +350,13 @@
 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 —
-for example, to alpha testers.
+would be to distribute a non-public version—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.
@@ -389,8 +390,8 @@
 
   <li>
     In the <b>Extension root directory</b> field,
-    specify the path to the extension's folder —
-    for example, <code>c:\myext</code>.
+    specify the path to the extension's folder—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.)
@@ -447,15 +448,15 @@
 
   <li>
     In the <b>Extension root directory</b> field,
-    specify the path to the extension's folder —
-    for example, <code>c:\myext</code>.
+    specify the path to the extension's folder—for example,

[Boris Smus, 2011/08/30 23:18:31]

Deliberately removed spaces around the hyphen?

+    <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 —
-    for example, <code>c:\myext.pem</code>.
+    already generated <code>.pem</code> file for this extension—for
+    example, <code>c:\myext.pem</code>.
   </li>
 
   <li>