Spruce extension packaging docs.

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

Index: chrome/common/extensions/docs/extensions/packaging.html
diff --git a/chrome/common/extensions/docs/extensions/packaging.html b/chrome/common/extensions/docs/extensions/packaging.html
index e46373c2ed4fb855f7b2bc7e09397d7d1023e264..9d6e8a924da44f62f81ae6f49bb073372df2c32a 100644
--- a/chrome/common/extensions/docs/extensions/packaging.html
+++ b/chrome/common/extensions/docs/extensions/packaging.html
@@ -231,7 +231,7 @@ with the file extension "crx"—for example,
 </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
@@ -245,8 +245,10 @@ Chrome Web Store getting started tutorial, starting at
 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>
 <a name="H2-0"></a><h2>Creating a package</h2>
 <p>To package an extension:</p>