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

chrome/common/extensions/docs/packaging.html

Index: chrome/common/extensions/docs/packaging.html
===================================================================
--- chrome/common/extensions/docs/packaging.html	(revision 138817)
+++ chrome/common/extensions/docs/packaging.html	(working copy)
@@ -132,6 +132,7 @@
                 <ul>
                   <li><a href="a11y.html">Accessibility</a></li>
                   <li><a href="background_pages.html">Background Pages</a></li>
+                  <li><a href="transient_background_pages.html">Event Pages</a></li>
                   <li><a href="content_scripts.html">Content Scripts</a></li>
                   <li><a href="xhr.html">Cross-Origin XHR</a></li>
                   <li><a href="i18n.html">Internationalization</a></li>
@@ -219,6 +220,15 @@
         <!-- STATIC CONTENT PLACEHOLDER -->
         <div id="static"><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,
@@ -227,8 +237,7 @@
 <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
@@ -242,8 +251,9 @@
 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>
 <a name="H2-0"></a><h2>Creating a package</h2>
 <p>To package an extension:</p>
@@ -330,17 +340,21 @@
 <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
+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