Spruce extension packaging docs.

This takes over for part of http://codereview.chromium.org/10455004/.


Review URL: https://chromiumcodereview.appspot.com/10825308

git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151168 0039d316-1c4b-4281-b951-d872f2087c98

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>

chrome/common/extensions/docs/server2/templates/articles/packaging.html

@@ -11,7 +11,7 @@ with the file extension "crx"—for example,
 
 <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
@@ -26,8 +26,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>
 
 

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

@@ -11,7 +11,7 @@ with the file extension "crx"—for example,
 
 <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
@@ -26,8 +26,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>