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

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

 <div id="pageData-title" class="pageData">Formats: Manifest Files</div>
 <div id="pageData-showTOC" class="pageData">true</div>
 
 <p>
 Every extension has a
 <a href="http://www.json.org">JSON</a>-formatted manifest file,
 named <code>manifest.json</code>,
 that provides important information about the extension.
 </p>
 
 <h2 id="overview"> Field summary </h2>
 
 <p>
 The following code shows the supported manifest fields,
 with links to the page that discusses each field.
 The only fields that are required for every extension
 are <b>name</b> and <b>version</b>.
 </p>
 
 <pre>
 {
   <b>"<a href="#name">name</a>"</b>: "<em>My Extension</em>",
   <b>"<a href="autoupdate.html">version</a>"</b>: "<em>versionString</em>",
 
   "<a href="#description">description</a>": "<em>A plain text description</em>",
   "<a href="#icons">icons</a>": { ... },
   "<a href="autoupdate.html">update_url</a>": "http://<em>path/to/updateInfo</em>.xml",
 
-  "<a href="background_pages.html">background_page</a>": "<em>aFile</em>.html", 
+  "<a href="background_pages.html">background_page</a>": "<em>aFile</em>.html",
   "<a href="content_scripts.html">content_scripts</a>": [...],
   "<a href="pageActions.html">page_actions</a>": [...],
   "<a href="#permissions">permissions</a>": [...],
   "<a href="npapi.html">plugins</a>": [...],
   "<a href="themes.html">theme</a>": [...],
   "<a href="toolstrip.html">toolstrips</a>": [...]
 }
 </pre>
 
 
@@ skipping 88 matching lines @@
 </pre>
 
 <p>
 For more information, see
 <a href="xhr.html">Cross-Origin XMLHttpRequest</a>,
 <a href="windows.html">Windows</a>,
 <a href="tabs.html">Tabs</a>, and
 <a href="bookmarks.html">Bookmarks</a>.
 </p>