Updates to hosting docs inline with policy changes

chrome/common/extensions/docs/templates/articles/hosting.html

Index: chrome/common/extensions/docs/templates/articles/hosting.html
diff --git a/chrome/common/extensions/docs/templates/articles/hosting.html b/chrome/common/extensions/docs/templates/articles/hosting.html
index 091e93b8d5a5efbb57f2e0de3b2e40bca6e9eb8d..683b1a81b3d84ba892833228c92517ee116f7757 100644
--- a/chrome/common/extensions/docs/templates/articles/hosting.html
+++ b/chrome/common/extensions/docs/templates/articles/hosting.html
@@ -1,5 +1,19 @@
 <h1>Hosting</h1>
 
+<p class="warning"><b>Warning:</b>
+As of Chrome 33,
+Windows stable/beta channel users can only download extensions
+hosted in the Chrome Web store,
+except for installs via
+<a href="https://support.google.com/chrome/a/answer/188453">enterprise policy</a>
+or
+<a href="getstarted.html#unpacked">developer mode</a>
+ (see
+ <a href="http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html">Protecting Windows users from malicious extensions</a>).
+You can still create your own <code>.crx</code> file and use it for testing in the dev channel,
+but you can't host that file on your own server.
+</p> 
+
 <p>
 This page tells you how to host <code>.crx</code> files
 on your own server.
@@ -81,4 +95,4 @@ that isn't in the previous list.
 To fix an HTTP header issue,
 either change the configuration of the server
 or try hosting the <code>.crx</code> file at another server.
-</p>
+</p>