Spruce extension packaging docs.

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>.
 </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.
+Be careful not to include your private key within
+your extensions!
 </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 143 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>