Modify the template to add analytics to all extension docs....

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

 <div id="pageData-title" class="pageData">Cross-Origin XMLHttpRequest</div>
 
 <!-- BEGIN AUTHORED CONTENT -->
 <p id="classSummary">
 Regular web pages can use the
 <a href="http://www.w3.org/TR/XMLHttpRequest/">XMLHttpRequest</a>
 object to send and receive data from remote servers,
 but they're limited by the
 <a href="http://en.wikipedia.org/wiki/Same_origin_policy">same origin policy</a>.
 Extensions aren't so limited.
@@ skipping 17 matching lines @@
 
 <p>If the extension attempts to use a security origin other than itself,
 say http://www.google.com,
 the browser disallows it
 unless the extension has requested the appropriate cross-origin permissions.
 </p>
 
 <h2 id="requesting-permission">Requesting cross-origin permissions</h2>
 
 <p>By adding hosts or host match patterns (or both) to the
-<a href="manifest.html#permissions">permissions<a> section of the 
-<a href="manifest.html">manifest</a> file, the extension can request access to 
+<a href="manifest.html#permissions">permissions</a> section of the
+<a href="manifest.html">manifest</a> file, the extension can request access to
 remote servers outside of its origin.</p>
 
 <pre>"permissions": [
   "http://www.google.com/",
 ],
 </pre>
 
 <p>Cross-origin permission values can be fully qualified host names,
 like these:</p>
 
@@ skipping 21 matching lines @@
 of hosts, it must declare the permissions separately:</p>
 
 <pre>"permissions": [
   "http://www.google.com/",
   "https://www.google.com/",
 ],
 </pre>
 
 
 <!-- END AUTHORED CONTENT -->