Remove .html extension from links

chrome/common/extensions/docs/templates/intros/webRequest.html

 <h2 id="manifest">Manifest</h2>
 <p>You must declare the "webRequest" permission in the <a
-  href="manifest.html">extension manifest</a> to use the web request
-API, along with <a href="declare_permissions.html">host permissions</a>
+  href="manifest">extension manifest</a> to use the web request
+API, along with <a href="declare_permissions">host permissions</a>
 for any hosts whose network requests you want to access. If you want to
 use the web request API in a blocking fashion, you need to request
 the "webRequestBlocking" permission in addition.
 For example:</p>
 <pre data-filename="manifest.json">
 {
   "name": "My extension",
   ...
   <b>"permissions": [
     "webRequest",
@@ skipping 95 matching lines @@
   <li>Pragma</li>
   <li>Proxy-Authorization</li>
   <li>Proxy-Connection</li>
   <li>Transfer-Encoding</li>
 </ul>
 </p>
 
 <p>
 The webRequest API only exposes requests that the extension has
 permission to see, given its
-<a href="declare_permissions.html">host permissions</a>.
+<a href="declare_permissions">host permissions</a>.
 Moreover, only the following schemes are accessible:
 <code>http://</code>,
 <code>https://</code>,
 <code>ftp://</code>,
 <code>file://</code>, or
 <code>chrome-extension://</code>.
 In addition, even certain requests with URLs using one of the above schemes
 are hidden, e.g.,
 <code>chrome-extension://other_extension_id</code> where
 <code>other_extension_id</code> is not the ID of the extension to handle
@@ skipping 19 matching lines @@
 
 <p>Each request is identified by a request ID. This ID is unique within a
 browser session and the context of an extension. It remains constant during the
 the life cycle of a request and can be used to match events for the same
 request. Note that several HTTP requests are mapped to one web request in case
 of HTTP redirection or HTTP authentication.</p>
 
 <h3 id="subscription">Registering event listeners</h3>
 
 <p>To register an event listener for a web request, you use a variation on the
-<a href="events.html">usual <code>addListener()</code> function</a>.
+<a href="events">usual <code>addListener()</code> function</a>.
 In addition to specifying a callback function,
 you have to specify a filter argument and you may specify an optional extra info
 argument.</p>
 
 <p>The three arguments to the web request API's <code>addListener()</code> have
 the following definitions:</p>
 <pre>
 var callback = function(details) {...};
 var filter = {...};
 var opt_extraInfoSpec = [...];
@@ skipping 21 matching lines @@
 cancelling or redirecting a request (<code>onBeforeRequest</code>), cancelling a
 request or modifying headers (<code>onBeforeSendHeaders</code>,
 <code>onHeadersReceived</code>), or providing authentication credentials
 (<code>onAuthRequired</code>).</p>
 
 <p>The $(ref:webRequest.RequestFilter)
 <code>filter</code> allows limiting the requests for which events are
 triggered in various dimensions:
 <dl>
   <dt>URLs</dt>
-  <dd><a href="match_patterns.html">URL patterns</a> such as
+  <dd><a href="match_patterns">URL patterns</a> such as
   <code>*://www.google.com/foo*bar</code>.</dd>
   <dt>Types</dt>
   <dd>Request types such as <code>main_frame</code> (a document that is loaded
   for a top-level frame), <code>sub_frame</code> (a document that is loaded for
   an embedded frame), and <code>image</code> (an image on a web site).
   See $(ref:webRequest.RequestFilter).</dd>
   <dt>Tab ID</dt>
   <dd>The identifier for one tab.</dd>
   <dt>Window ID</dt>
   <dd>The identifier for a window.</dd>
@@ skipping 78 matching lines @@
         details.requestHeaders.splice(i, 1);
         break;
       }
     }
     return {requestHeaders: details.requestHeaders};
   },
   {urls: ["&lt;all_urls&gt;"]},
   ["blocking", "requestHeaders"]);
 </pre>
 
-<p> For more example code, see the <a href="samples.html#webrequest">web request
+<p> For more example code, see the <a href="samples#webrequest">web request
 samples</a>.</p>