Remove .html extension from links

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

 <h2 id="manifest">Manifest</h2>
 
 <p>
 You must declare the "declarativeWebRequest" permission in the
-<a href="manifest.html">extension manifest</a> to use this API,
-along with <a href="declare_permissions.html">host permissions</a>.
+<a href="manifest">extension manifest</a> to use this API,
+along with <a href="declare_permissions">host permissions</a>.
 </p>
 
 <pre data-filename="manifest.json">
 {
   "name": "My extension",
   ...
 <b>  "permissions": [
     "declarativeWebRequest",
     "*://*/*"
   ]</b>,
@@ skipping 27 matching lines @@
 "http://something.else.com"
 </ul>
 The extension cannot set up a rule to redirect "http://www.google.com" to
 "http://mail.google.com".
 </p>
 
 <h2 id="rules">Rules</h2>
 
 <p>
 The Declarative Web Request API follows the concepts of the <a
-  href="events.html#declarative">Declarative API</a>. You can register rules to
+  href="events#declarative">Declarative API</a>. You can register rules to
 the <code>chrome.declarativeWebRequest.onRequest</code> event object.
 </p>
 
 <p>
 The Declarative Web Request API supports a single type of match criteria, the
 <code>RequestMatcher</code>. The <code>RequestMatcher</code> matches network
 requests if and only if all listed criteria are met. The following
 <code>RequestMatcher</code> would match a network request when the user enters
 "http://www.example.com" in the URL bar:
 </p>
@@ skipping 54 matching lines @@
 </p>
 <pre>
 chrome.declarativeWebRequest.onRequest.addRules([rule2]);
 </pre>
 
 <p class="note">
 <strong>Note:</strong> You should always register or unregister rules in bulk rather than
 individually because each of these operations recreates internal data
 structures.  This re-creation is computationally expensive but facilitates a
 very fast URL matching algorithm for hundreds of thousands of URLs. The
-<a href="events.html#performance">Performance section</a> of the
+<a href="events#performance">Performance section</a> of the
 $(ref:events Events) API provides further performance tips.
 </p>
 
 
 <h2 id="evaluation">Evaluation of conditions and actions</h2>
 
 <p>
 The Declarative Web Request API follows the
-<a href="webRequest.html#life_cycle">Life cycle model for web requests</a> of
-the <a href="webRequest.html">Web Request API</a>. This means that conditions
+<a href="webRequest#life_cycle">Life cycle model for web requests</a> of
+the <a href="webRequest">Web Request API</a>. This means that conditions
 can only be tested at specific stages of a web request and, likewise, actions
 can also only be executed at specific stages. The following tables list the
 request stages that are compatible with conditions and actions.
 </p>
 
 <p>
 <table>
   <tr>
     <th colspan="5">Request stages during which condition attributes can be processed.
   </tr>
@@ skipping 60 matching lines @@
 action because both of them can be evaluated in the onHeadersReceived stage.
 It is, however, impossible to combine the request matcher with a
 <code>new chrome.declarativeWebRequest.SetRequestHeader()</code>
 because request headers cannot be set any more by the time the content type has been terminated.
 </p>
 
 <h2 id="precedences">Using priorities to override rules</h2>
 
 <p>
 Rules can be associated with priorities as described in the
-<a href="events.html#declarative">Events API</a>. This mechanism can be used
+<a href="events#declarative">Events API</a>. This mechanism can be used
 to express exceptions. The following example will block all requests to
 images named "evil.jpg" except on the server "myserver.com".
 </p>
 
 <pre>
 var rule1 = {
   priority: 100,
   conditions: [
     new chrome.declarativeWebRequest.RequestMatcher({
         url: { pathEquals: 'evil.jpg' } })
@@ skipping 16 matching lines @@
 chrome.declarativeWebRequest.onRequest.addRules([rule1, rule2]);
 </pre>
 
 <p>
 It is important to recognize that the <code>IgnoreRules</code> action is not
 persisted across <a href="#evaluation">request stages</a>. All conditions of
 all rules are evaluated at each stage of a web request. If an
 <code>IgnoreRules</code> action is executed, it applies only to other actions
 that are executed for the same web request in the same stage.
 </p>