Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
diff --git a/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html b/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
index 7de1ce8f84a33a775808dac55920d1e087ab33a2..8dabcb389d1c575dfcd1fd6c5406b8a6b79909f1 100644
--- a/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
+++ b/chrome/common/extensions/docs/templates/intros/declarativeWebRequest.html
@@ -2,8 +2,8 @@
 
 <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">
@@ -51,7 +51,7 @@ The extension cannot set up a rule to redirect "http://www.google.com" to
 
 <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>
 
@@ -126,7 +126,7 @@ chrome.declarativeWebRequest.onRequest.addRules([rule2]);
 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>
 
@@ -135,8 +135,8 @@ $(ref:events Events) API provides further performance tips.
 
 <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.
@@ -217,7 +217,7 @@ because request headers cannot be set any more by the time the content type has
 
 <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>