Remove .html extension from links

chrome/common/extensions/docs/templates/articles/tut_migration_to_manifest_v2.html

 <h1>Tutorial: Migrate to Manifest V2</h1>
 
 <p>
 Manifest version 1 was deprecated in Chrome 18,
 and support will be phased out according to the
-<a href="manifestVersion.html#manifest-v1-support-schedule">manifest version 1 support schedule</a>.
+<a href="manifestVersion#manifest-v1-support-schedule">manifest version 1 support schedule</a>.
 The changes from version 1 to version 2
 fall under two broad categories:
 API changes and Security changes. 
 </p>
 
 <p>
 This document provides checklists for migrating your Chrome extensions
 from manifest version 1 to version 2,
 followed by more detailed summaries of what these changes mean and why they were made.
 </p>
@@ skipping 37 matching lines @@
       <li>Replace with <code>chrome.extension.getViews( { "type" : "tab" } )</code>.</li>
     </ul>
   <li>Does your extension use a background page?</li>
     <ul>
       <li>Replace the <code>background_page</code> property
         with a <code>background</code> property.</li>
       <li>Add a <code>scripts</code> or <code>page</code>
         property that contains the code for the page.</li>
       <li>Add a <code>persistent</code> property and set it
         to <code>false</code> to convert your background page
-        to an <a href="event_pages.html">event page</a></li>
+        to an <a href="event_pages">event page</a></li>
     </ul>
 </ul>
 
 <h2 id="security-checklist">Security changes checklist</h2>
 
 <ul>
   <li>Are you using inline script blocks in HTML pages?</li>
     <ul>
       <li>Remove JS code contained within &lt;script> tags
         and place it within an external JS file.</li>
     </ul>
   <li>Are you using inline event handlers (like onclick, etc)?</li>
     <ul>
       <li>Remove them from the HTML code,
         move them into an external JS file and
         use <code>addEventListener()</code> instead.</li>
     </ul>
   <li>Does your extension inject content scripts into Web pages
     that need to access resources (like images and scripts)
     that are contained in the extension’s package?</li>
     <ul>
-      <li>Define the <a href="manifest/web_accessible_resources.html">web_accessible_resources</a>
+      <li>Define the <a href="manifest/web_accessible_resources">web_accessible_resources</a>
         property and list the resources
         (and optionally a separate Content Security Policy for those resources).</li>
     </ul>
   <li>Does your extension embed external Web pages?</li>
     <ul>
-      <li>Define the <a href="manifest/sandbox.html">sandbox</a> property.</li>
+      <li>Define the <a href="manifest/sandbox">sandbox</a> property.</li>
     </ul>
   <li>Is your code or library using <code>eval()</code>, new <code>Function()</code>,
     <code>innerHTML</code>, <code>setTimeout()</code>, or otherwise passing strings
     of JS code that are dynamically evaluated?</li>
     <ul>
       <li>Use <code>JSON.parse()</code>
         if you’re parsing JSON code into an object.</li>
       <li>Use a CSP-friendly library,
         for example, <a href="http://angularjs.org/">AngularJS</a>.</li>
       <li>Create a sandbox entry in your manifest and
@@ skipping 65 matching lines @@
 </ul>
 
 <h3 id="removed_and_changed">Removed and changed APIs</h3>
 
 <p>
 A few extension APIs have been removed and replaced with new counterparts:
 </p>
 
 <ul>
   <li>The <code>background_page</code> property has been replaced
-    by <a href="background_pages.html">background</a>.</li>
+    by <a href="background_pages">background</a>.</li>
   <li>The <code>chrome.self</code> property has been removed,
     use <code>chrome.extension</code>.</li>
   <li>The <code>Port.tab</code> property has been replaced
     with <code>Port.sender</code>.</li>
   <li>The <code>chrome.extension.getTabContentses()</code> and the
     <code>chrome.extension.getExtensionTabs()</code> APIs have been replaced
     by <code>chrome.extension.getViews( { "type" : "tab" } )</code>.</li>
 </ul>
 
 <h2 id="security-summary">Summary of security changes</h2>
 
 <p>
 There are a number of security-related changes
 that accompany the move from manifest version 1 to version 2.
 Many of these changes stem from Chrome’s adoption of
-<a href="contentSecurityPolicy.html">Content Security Policy</a>;
+<a href="contentSecurityPolicy">Content Security Policy</a>;
 you should read more about this policy to understand its implications.
 </p>
 
 <h3 id="inline_scripts">Inline scripts and event handlers disallowed</h3>
 
 <p>
-Due to the use of <a href="contentSecurityPolicy.html">Content Security Policy</a>,
+Due to the use of <a href="contentSecurityPolicy">Content Security Policy</a>,
 you can no longer use &lt;script> tags that are inline with the HTML content.
 These must be moved to external JS files.
 In addition, inline event handlers are also not supported.
 For example, suppose you had the following code in your extension:
 </p>
 
 <pre>
 &lt;html>
 &lt;head>
   &lt;script>
@@ skipping 45 matching lines @@
 <p>
 There are some scenarios where your extension might embed content
 that can be used externally or come from an external source. 
 </p>
 
 <p>
 <strong>Extension content in web pages:</strong><br>
 If your extension embeds resources (like images, script, CSS styles, etc)
 that are used in content scripts that are injected into web pages,
 you need to use the
-<a href="manifest/web_accessible_resources.html">web_accessible_resources</a> property
+<a href="manifest/web_accessible_resources">web_accessible_resources</a> property
 to whitelist these resources so that external Web pages can use them:
 </p>
 
 <pre data-filename="manifest.json">
 { 
 ...
   "<strong>web_accessible_resources</strong>": [
     "images/image1.png",
     "script/myscript.js"
   ],
@@ skipping 52 matching lines @@
 <ol>
   <li>Create a sandbox entry in your manifest file.</li>
   <li>In the sandbox entry,
     list the pages you want to run in the sandbox.</li>
   <li>Use message passing via <code>postMessage()</code>
     to communicate with the sandboxed page.</li>
 </ol>
 
 <p>
 For more details on how to do this,
-see the <a href="sandboxingEval.html">Sandboxing Eval</a> documentation.
+see the <a href="sandboxingEval">Sandboxing Eval</a> documentation.
 </p>
 
 <h2 id="further-reading">Further reading</h2>
 
 <p>
 The changes in manifest version 2 are designed to guide developers
 toward building more secure and robustly-architected extensions and apps.
 To see a complete list of changes from manifest version 1 to version 2,
-see the <a href="manifestVersion.html">manifest file</a> documentation.
+see the <a href="manifestVersion">manifest file</a> documentation.
 For more information about using sandboxing to isolate unsafe code,
-read the <a href="sandboxingEval.html">sandboxing eval</a> article.
+read the <a href="sandboxingEval">sandboxing eval</a> article.
 You can learn more about Content Security Policy
 by visiting our extensions-related tutorial and a
 <a href="http://www.html5rocks.com/en/tutorials/security/content-security-policy/">good introduction on HTML5Rocks</a>.
 </p>