Extensions Docs Server: Doc conversion script

chrome/common/extensions/docs/server2/templates/intros/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
 efficiency.
 </p>
 <h2 id="manifest">Manifest</h2>
 <p>
 You must declare the "declarative" and the "declarativeWebRequest" permission in
 the <a href="manifest.html">extension manifest</a> to use this API,
 along with <a href="manifest.html#permissions">host permissions</a> for any
 hosts whose network requests you want to access. 
 </p>
 <pre>{
   "name": "My extension",
   ...
 <b>  "permissions": [
-    "declarative",
     "declarativeWebRequest",
     "*://*.google.com"
   ]</b>,
   ...
 }</pre>
 <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
 the <code>chrome.declarativeWebRequest.onRequest</code> event object.
@@ skipping 63 matching lines @@
 structures.  This re-creation is computationally expensive but facilitates a
 very fast URL matching algorithm for hundreds of thousands of URLs.
 </p>
 <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 -->
+</ul>