Remove .html extension from links

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 683b1a81b3d84ba892833228c92517ee116f7757..eec00a05a5f7c8ba1611032ab5fdd1896a7d7b3f 100644
--- a/chrome/common/extensions/docs/templates/articles/hosting.html
+++ b/chrome/common/extensions/docs/templates/articles/hosting.html
@@ -7,7 +7,7 @@ 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>
+<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,
@@ -22,7 +22,7 @@ If you distribute your extension, app, or theme solely through the
 you don't need this page.
 Instead, consult the
 <a href="http://www.google.com/support/chrome_webstore/">store help</a> and
-<a href="http://code.google.com/chrome/webstore/index.html">developer documentation</a>.
+<a href="http://code.google.com/chrome/webstore/index">developer documentation</a>.
 </p>
 
 <p>
@@ -38,9 +38,9 @@ the dashboard creates the <code>.crx</code> file for you.
 <p>
 If you aren't publishing using the dashboard,
 you need to create the <code>.crx</code> file yourself,
-as described in <a href="packaging.html">Packaging</a>.
+as described in <a href="packaging">Packaging</a>.
 You can also specify
-<a href="autoupdate.html">autoupdate</a> information to ensure that
+<a href="autoupdate">autoupdate</a> information to ensure that
 your users will have the latest copy of the <code>.crx</code> file.
 </p>