Remove .html extension from links

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

 <h1>Content Scripts</h1>
 
 
 <p>
 Content scripts are JavaScript files that run in the context of web pages.
 By using the standard
 <a href="http://www.w3.org/TR/DOM-Level-2-HTML/">Document
 Object Model</a> (DOM),
 they can read details of the web pages the browser visits,
 or make changes to them.
@@ skipping 11 matching lines @@
 
 <p>
 However, content scripts have some limitations.
 They <b>cannot</b>:
 </p>
 
 <ul>
   <li>
     Use chrome.* APIs
     (except for parts of
-    <a href="extension.html"><code>chrome.extension</code></a>)
+    <a href="extension"><code>chrome.extension</code></a>)
   </li>
   <li>
     Use variables or functions defined by their extension's pages
   </li>
   <li>
     Use variables or functions defined by web pages or by other content scripts
   </li>
 </ul>
 
 <p>
 These limitations aren't as bad as they sound.
 Content scripts can <em>indirectly</em> use the chrome.* APIs,
 get access to extension data,
 and request extension actions
-by exchanging <a href="messaging.html">messages</a>
+by exchanging <a href="messaging">messages</a>
 with their parent extension.
 Content scripts can also
-make <a href="xhr.html">cross-site XMLHttpRequests</a>
+make <a href="xhr">cross-site XMLHttpRequests</a>
 to the same sites as their parent extensions,
 and they can
 <a href="#host-page-communication">communicate with web pages</a>
 using the shared DOM.
 For more insight into what content scripts can and can't do,
 learn about the
 <a href="#execution-environment">execution environment</a>.
 </p>
 
 <h2 id="registration">Manifest</h2>
 
 <p>If your content script's code should always be injected,
 register it in the
-<a href="manifest.html">extension manifest</a>
+<a href="manifest">extension manifest</a>
 using the <code>content_scripts</code> field,
 as in the following example.
 </p>
 
 <pre data-filename="manifest.json">
 {
   "name": "My extension",
   ...
   <b>"content_scripts": [
     {
       "matches": ["http://www.google.com/*"],
       "css": ["mystyles.css"],
       "js": ["jquery.js", "myscript.js"]
     }
   ]</b>,
   ...
 }
 </pre>
 
 <p>
 If you want to inject the code only sometimes,
 use the
-<a href="declare_permissions.html"><code>permissions</code></a> field instead,
+<a href="declare_permissions"><code>permissions</code></a> field instead,
 as described in <a href="#pi">Programmatic injection</a>.
 </p>
 
 <pre data-filename="manifest.json">
 {
   "name": "My extension",
   ...
   <b>"permissions": [
     "tabs", "http://www.google.com/*"
   ]</b>,
@@ skipping 12 matching lines @@
   <tr>
     <th>Name</th>
     <th>Type</th>
     <th>Description</th>
   </tr>
   <tr>
     <td><code>matches</code></td>
     <td>array of strings</td>
     <td><em>Required.</em>
     Specifies which pages this content script will be injected into.
-    See <a href="match_patterns.html">Match Patterns</a>
+    See <a href="match_patterns">Match Patterns</a>
     for more details on the syntax of these strings
     and <a href="#match-patterns-globs">Match patterns and globs</a>
     for information on how to exclude URLs.</td>
   </tr>
   <tr>
     <td><code>exclude_matches</code></td>
     <td>array of strings</td>
     <td><em>Optional.</em>
     Excludes pages that this content script would otherwise be
     injected into.
-    See <a href="match_patterns.html">Match Patterns</a>
+    See <a href="match_patterns">Match Patterns</a>
     for more details on the syntax of these strings
     and <a href="#match-patterns-globs">Match patterns and globs</a>
     for information on how to exclude URLs.</td>
   </tr>
   <tr>
     <td><code>css<code></td>
     <td>array of strings</td>
     <td><em>Optional.</em>
     The list of CSS files to be injected into matching pages. These are injected in the order they appear in this array, before any DOM is constructed or displayed for the page.</td>
   </tr>
@@ skipping 63 matching lines @@
 For example, assume <code>matches</code> is <code>["http://*.nytimes.com/*"]</code>:
 </p>
 <ul>
 <li>If <code>exclude_matches</code> is <code>["*://*/*business*"]</code>, then the content script would be injected into "http://www.nytimes.com/health" but not into "http://www.nytimes.com/business".</li>
 <li>If <code>include_globs</code> is <code>["*nytimes.com/???s/*"]</code>, then the content script would be injected into "http:/www.nytimes.com/arts/index.html" and "http://www.nytimes.com/jobs/index.html" but not into "http://www.nytimes.com/sports/index.html".</li>
 <li>If <code>exclude_globs</code> is <code>["*science*"]</code>, then the content script would be injected into "http://www.nytimes.com" but not into "http://science.nytimes.com" or "http://www.nytimes.com/science".</li>
 </ul>
 <p>
 
 <p>
-Glob properties follow a different, more flexible syntax than <a href="match_patterns.html">match patterns</a>.  Acceptable glob strings are URLs that may contain "wildcard" asterisks and question marks. The asterisk (*) matches any string of any length (including the empty string); the question mark (?) matches any single character.
+Glob properties follow a different, more flexible syntax than <a href="match_patterns">match patterns</a>.  Acceptable glob strings are URLs that may contain "wildcard" asterisks and question marks. The asterisk (*) matches any string of any length (including the empty string); the question mark (?) matches any single character.
 </p>
 
 <p>
 For example, the glob "http://???.example.com/foo/*" matches any of the following:
 </p>
 <ul>
   <li>"http://www.example.com/foo/bar"</li>
   <li>"http://the.example.com/foo/"</li>
 </ul>
 <p>
@@ skipping 12 matching lines @@
 when your JavaScript or CSS code
 shouldn't be injected into every single page
 that matches the pattern &mdash;
 for example, if you want a script to run
 only when the user clicks a browser action's icon.
 </p>
 
 <p>
 To insert code into a page,
 your extension must have
-<a href="xhr.html#requesting-permission">cross-origin permissions</a>
+<a href="xhr#requesting-permission">cross-origin permissions</a>
 for the page.
 It also must be able to use the <code>chrome.tabs</code> module.
 You can get both kinds of permission
 using the manifest file's
-<a href="declare_permissions.html">permissions</a> field.
+<a href="declare_permissions">permissions</a> field.
 </p>
 
 <p>
 Once you have permissions set up,
 you can inject JavaScript into a page by calling
 $(ref:tabs.executeScript).
 To inject CSS, use
 $(ref:tabs.insertCSS).
 </p>
 
@@ skipping 100 matching lines @@
   window.postMessage({ type: "FROM_PAGE", text: "Hello from the webpage!" }, "*");
 }, false);</pre>
 <p>In the above example, example.html (which is not a part of the extension) posts messages to itself, which are intercepted and inspected by the content script, and then posted to the extension process. In this way, the page establishes a line of communication to the extension process. The reverse is possible through similar means.</p>
 
 <h2 id="security-considerations">Security considerations</h2>
 
 <p>When writing a content script, you should be aware of two security issues.
 First, be careful not to introduce security vulnerabilities into the web site
 your content script is injected into.  For example, if your content script
 receives content from another web site (for example, by making an <a
-href="xhr.html">XMLHttpRequest</a>),
+href="xhr">XMLHttpRequest</a>),
 be careful to filter that content for <a
 href="http://en.wikipedia.org/wiki/Cross-site_scripting">cross-site
 scripting</a> attacks before injecting the content into the current page.
 For example, prefer to inject content via innerText rather than innerHTML.
 Be especially careful when retrieving HTTP content on an HTTPS page because
 the HTTP content might have been corrupted by a network <a
 href="http://en.wikipedia.org/wiki/Man-in-the-middle_attack">"man-in-the-middle"</a>
 if the user is on a hostile network.</p>
 
 <p>Second, although running your content script in an isolated world provides
@@ skipping 38 matching lines @@
 <pre>
 <em>//Code for displaying &lt;extensionDir>/images/myimage.png:</em>
 var imgURL = <b>chrome.extension.getURL("images/myimage.png")</b>;
 document.getElementById("someImage").src = imgURL;
 </pre>
 
 <h2 id="examples"> Examples </h2>
 
 <p>
 You can find many
-<a href="samples.html#script">examples that use content scripts</a>.
+<a href="samples#script">examples that use content scripts</a>.
 A simple example of communication via messages is in the
-<a href="samples.html#message-timer">Message Timer</a>.
-See <a href="samples.html#page-redder">Page Redder</a> and
-<a href="samples.html#email-this-page-(by-google)">Email This Page</a>
+<a href="samples#message-timer">Message Timer</a>.
+See <a href="samples#page-redder">Page Redder</a> and
+<a href="samples#email-this-page-(by-google)">Email This Page</a>
 for examples of programmatic injection.
 </p>
 
 
 <h2 id="videos"> Videos </h2>
 
 <p>
 The following videos discuss concepts that are important for content scripts.
 The first video describes content scripts and isolated worlds.
 </p>
 
 <p>
 <iframe title="YouTube video player" width="640" height="390" src="//www.youtube.com/embed/laLudeUmXHM?rel=0" frameborder="0" allowfullscreen></iframe>
 </p>
 
 <p>
 The next video describes message passing,
 featuring an example of a content script
 sending a request to its parent extension.
 </p>
 
 <p>
 <iframe title="YouTube video player" width="640" height="390" src="//www.youtube.com/embed/B4M_a7xejYI?rel=0" frameborder="0" allowfullscreen></iframe>
 </p>