Remove .html extension from links

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

 <h1>Other Deployment Options</h1>
 
 <p>
 Usually, users install their own extensions.
 But sometimes you might want an extension
 to be installed automatically.
 Here are two typical cases:
 </p>
 
 <ul>
@@ skipping 26 matching lines @@
 Both ways support installing an extension hosted at an
 <code>update_URL</code>.
 In the Windows registry,
 the <code>update_URL</code> must point to the Chrome Web Store
 where the extension is hosted.
 </p>
 
 <p>
 In the preferences file,
 it can point to your own server where you are hosting the extension
-(see <a href="autoupdate.html#update_url">autoupdating</a>).
+(see <a href="autoupdate#update_url">autoupdating</a>).
 The preferences JSON file also supports installing
 an extension from a <code>.crx</code> extension
 file on the user's computer
-(see <a href="hosting.html">hosting</a>).
+(see <a href="hosting">hosting</a>).
 </p>
 
 
 <p class="note">
 <b>Install extensions from your website:</b>
 The safest option for your users is to publish your extension
 in the Chrome Web Store.
 Instead of hosting your own extension,
 publish it in the store, and link to the store install using
 <a href="https://developers.google.com/chrome/web-store/docs/inline_installation">inline installation</a>.
 </p>
 
 <h2 id="prereqs">Before you begin</h2>
 
 <p>
-First, <a href="/webstore/publish.html">publish</a>
+First, <a href="/webstore/publish">publish</a>
 the extension in the Chrome Web Store,
-or package a <a href="packaging.html"><code>.crx</code> file</a>
+or package a <a href="packaging"><code>.crx</code> file</a>
 and make sure that it installs successfully.
 </p>
 
 
 <p class="warning">
 <b>Windows installs must come from Chrome Web Store:</b><br>
 As of Chrome 33,
 no external installs are allowed from a path to a local <code>.crx</code>
 (see <a href="http://blog.chromium.org/2013/11/protecting-windows-users-from-malicious.html">Protecting Windows users from malicious extensions</a>).
 </p>
 
 <p>
 If installing from an
- <a href="autoupdate.html#update_url">update URL</a>, ensure that the extension
-is properly <a href="hosting.html">hosted</a>.
+ <a href="autoupdate#update_url">update URL</a>, ensure that the extension
+is properly <a href="hosting">hosted</a>.
 </p>
 
 <p>
 Before you edit the preferences file or the registry,
 make a note of the following:
 </p>
 
 <ul>
  <li> The intended <b>location</b> of the extension's <code>.crx</code> file,
         or the update URL from which it is served </li>
@@ skipping 177 matching lines @@
 <p><b>Will the methodology for allowing a “pre-install” still be supported
 by Google Chrome from M33 onwards?</b></p>
 <p>Yes, but only as an install from a Chrome Web Store
 <code>update_URL</code>,
 not from a local file path.</p> 
 
 <p><b>Can I specify a URL as a path to the external extension?</b> </p>
 <p>Yes, use the <a href="#preferences">preferences JSON</a> file
 for Mac OS X and Linux; the <a href="#registry">registry</a> for Windows.
 The extension must be hosted as explained in
-<a href="hosting.html">hosting</a>.
+<a href="hosting">hosting</a>.
 In the preferences file,
 use the "external_update_url" property to point to an
-<a href="autoupdate.html#update_manifest">update manifest</a> that has the URL for your
+<a href="autoupdate#update_manifest">update manifest</a> that has the URL for your
 extension.
 In the Windows registry,
 use the "update_url" property.</p>
 
 <p><b>What are some common mistakes when installing with the preferences
 file?</b></p>
 <ul>
   <li>
     Not specifying the same id/version
     as the one listed in the <code>.crx</code> </li>
@@ skipping 25 matching lines @@
   <li>Permissions problems on a network share </li>
 </ul>
 
 <p><b>How do I update my native binaries and extension in-step?</b></p>
 <p>Previously when off-store extensions were supported,
 it was possible to have the native binaries and the extension be updated in lock step.
 However, extensions hosted on the Chrome Web Store are updated
 via the Chrome update mechanism which developers do not control.
 Extension developers should be careful about updating extensions
 that have a dependency on the native binary
-(for example, legacy extensions using <a href="npapi.html">NPAPI</a>).
+(for example, legacy extensions using <a href="npapi">NPAPI</a>).
 </p>
 
 <p><b>What if the user uninstalls the extension?</b> </p>
 <p>If the user uninstalls the extension through the UI, it will no
 longer be installed or updated on each startup. In other words, the
 external extension is blacklisted. </p>
 
 <p><b>How do I get off the blacklist?</b> </p>
 <p>If the user uninstalls your extension, you should respect that
 decision. However, if you (the developer) accidentally uninstalled
 your extension through the UI,
 you can remove the blacklist tag
 by installing the extension normally
 through the UI, and then uninstalling it. </p>