Making sure self-hosting and packaging docs are clear about keeping private key secure

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

 <div id="pageData-name" class="pageData">Packaging</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
+<p class="note">
+<b>For Advanced Developers Only:</b>
+Do not follow the instructions on this page
+unless you understand the security implications
+of packaging and hosting files on your own server.
+If you host on the Chrome Web Store,
+you do not need to worry
+about packaging or self-hosting.
+</p>
+
 <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>.
 </p>
 
 <p>
-<b>Note:</b>
-You might not need to package your extension.
+You do not need to package your own 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.
 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>
 
 <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.
+The private key is used to sign each version of the extension
+and must be secured from public access.
+Do not store the private key in your packaged files.
 </p>
 
 
 <h2>Creating a package</h2>
 
 <p>To package an extension:</p>
 <ol>
   <li>
     Bring up the Extensions management page
     by going to this URL:
@@ skipping 92 matching lines @@
 
 <img src="images/update-success.gif"
   width="298" height="160" />
 
 
 <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.
+However, a new extension ID will be created

[Aaron Boodman, 2012/06/06 18:27:26]

I don't think this section needs to change. The previous version seems more
clear to me.

+in the Chrome Web Store.
+You must ensure that only one extension ID is used.
+If you've already distributed your extension package,
+replace the newly created extension ID
+with your existing extension ID.
+Otherwise, users can install multiple versions
+of your extension, each with its own local data.
+If you haven't distributed your extension package,
+you can use the new extension ID,
+taking care to remove any references to the old one.
 </p>
 
 <p>
-If you want to keep the extension ID the same,
-follow these steps:
+To replace the newly created extension ID
+with your existing extension ID:
 </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>
@@ skipping 19 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>