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

chrome/common/extensions/docs/hosting.html

Index: chrome/common/extensions/docs/hosting.html
===================================================================
--- chrome/common/extensions/docs/hosting.html	(revision 138817)
+++ chrome/common/extensions/docs/hosting.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>
@@ -192,6 +193,15 @@
         <!-- Standard content lead-in for experimental API pages -->
         <!-- STATIC CONTENT PLACEHOLDER -->
         <div id="static"><div id="pageData-name" class="pageData">Hosting</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 tells you how to host <code>.crx</code> files
 on your own server.