Move declarative API into events API

chrome/common/extensions/docs/static/declarativeWebRequest.html

 <!-- BEGIN AUTHORED CONTENT -->
 
 <h2 id="notes">Notes</h2>
 
 <p>
 Use the <code>chrome.declarativeWebRequest</code> module to intercept, block, or
 modify requests in-flight. It is significantly faster than the <a
   href="webRequest.html"><code>chrome.webRequest</code> API</a> because you can
 register rules that are evaluated in the browser rather than the
 JavaScript engine which reduces roundtrip latencies and allows for very high
@@ skipping 17 matching lines @@
     "declarativeWebRequest",
     "*://*.google.com"
   ]</b>,
   ...
 }</pre>
 
 <h2 id="rules">Rules</h2>
 
 <p>
 The Declarative Web Request API follows the concepts of the <a
-  href="declarative.html">Declarative API</a>. You can register rules to the
-<code>chrome.declarativeWebRequest.onRequest</code> event object.
+  href="events.html#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 65 matching lines @@
 <h2 id="TODO">Todo</h2>
 <ul>
   <li>Explain precedences, once we can ignore rules based on their priority
   (e.g. how can I cancel all requests except for a specific whitelist?)
   <li>Explain when conditions can be evaluated, when actions can be executed,
   and when rules can be executed (e.g. you cannot cancel a request when you
   have received the response already)
 </ul>
 
 <!-- END AUTHORED CONTENT -->