Add info about providing the .pem file if you've previously

chrome/common/extensions/docs/packaging.html

Index: chrome/common/extensions/docs/packaging.html
===================================================================
--- chrome/common/extensions/docs/packaging.html	(revision 99365)
+++ chrome/common/extensions/docs/packaging.html	(working copy)
@@ -272,19 +272,26 @@
                 </li>
               </ol>
             </li><li>
-              <a href="#H2-2">Packaging at the command line</a>
+              <a href="#upload"> Uploading a previously packaged extension to the Chrome Web Store</a>
               <ol>
                 <li style="display: none; ">
                   <a>h3Name</a>
                 </li>
               </ol>
             </li><li>
-              <a href="#H2-3">Package format and scripts</a>
+              <a href="#H2-3">Packaging at the command line</a>
               <ol>
                 <li style="display: none; ">
                   <a>h3Name</a>
                 </li>
               </ol>
+            </li><li>
+              <a href="#H2-4">Package format and scripts</a>
+              <ol>
+                <li style="display: none; ">
+                  <a>h3Name</a>
+                </li>
+              </ol>
             </li>
               <li style="display: none; ">
                 <a href="#apiReference">API reference</a>
@@ -415,8 +422,7 @@
 </p>
 <ul>
 <li><a href="#update">Update</a> the extension</li>
-<li>Upload the extension using the
-<a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a></li>
+<li><a href="#upload">Upload</a> the extension to the Chrome Web Store</li>
 </ul>
 
 <p>
@@ -468,9 +474,40 @@
 
 <img src="images/update-success.gif" width="298" height="160">
 
-<a name="H2-2"></a><h2>Packaging at the command line</h2>
 
+<h2 id="upload"> Uploading a previously packaged extension to the Chrome Web Store</h2>
+
 <p>
+You can use the Chrome Developer Dashboard
+to upload an extension that you've previously packaged yourself.
+However, unless you take special steps,
+the extension's ID in the Chrome Web Store
+will be different from its ID in the package you created.
+This different ID might be a problem if you've
+distributed your extension package,
+because it allows users to install multiple versions of your extension,
+each with its own local data.
+</p>
+
+<p>
+If you want to keep the extension ID the same,
+follow these steps:
+</p>
+
+<ol>
+  <li> Rename the private key that was generated
+    when you created the <code>.crx</code> file to <code>key.pem</code>. </li>
+  <li> Put <code>key.pem</code> in the top directory
+    of your extension. </li>
+  <li> Compress that directory into a ZIP file. </li>
+  <li> Upload the ZIP file using the
+    <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a>. </li>
+</ol>
+
+
+<a name="H2-3"></a><h2>Packaging at the command line</h2>
+
+<p>
 Another way to package extensions
 is by invoking <code>chrome.exe</code> at the command line.
 Use the <code>--pack-extension</code> flag
@@ -488,7 +525,7 @@
 add <code>--no-message-box</code> to the command.
 </p>
 
-<a name="H2-3"></a><h2>Package format and scripts</h2>
+<a name="H2-4"></a><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>.