Updating extension hosting docs

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

 <h1>Hosting</h1>
 
 <p class="warning"><b>Warning:</b>
 As of Chrome 33,
-Windows stable/beta channel users can only download extensions
+Windows 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#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.
+As of Chrome 44, no external installs are allowed from a path to a local .crx on Mac
+(see
+<a href="http://blog.chromium.org/2015/05/continuing-to-protect-chrome-users-from.html">Continuing to protect Chrome users from malicious extensions</a>).
 </p> 
 
 <p>
 This page tells you how to host <code>.crx</code> files
 on your own server.
 If you distribute your extension, app, or theme solely through the
 <a href="http://chrome.google.com/webstore">Chrome Web Store</a>,
 you don't need this page.
 Instead, consult the
 <a href="http://www.google.com/support/chrome_webstore/">store help</a> and
@@ skipping 64 matching lines @@
 The most common reason for failing to recognize an installable file
 is that the server sends the header
 <code>X-Content-Type-Options: nosniff</code>.
 The second most common reason
 is that the server sends an unknown content type&mdash;one
 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>