Remove .html extension from links

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

 <h1>Cross-Origin XMLHttpRequest</h1>
 
 
 <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="declare_permissions.html">permissions</a> section of the
-<a href="manifest.html">manifest</a> file, the extension can request access to
+<a href="declare_permissions">permissions</a> section of the
+<a href="manifest">manifest</a> file, the extension can request access to
 remote servers outside of its origin.</p>
 
 <pre data-filename="manifest.json">
 {
   "name": "My extension",
   ...
   <b>"permissions": [
     "http://www.google.com/"
   ]</b>,
   ...
@@ skipping 11 matching lines @@
 <p>Or they can be match patterns, like these:</p>
 
 <ul>
   <li> "http://*.google.com/" </li>
   <li> "http://*/" </li>
 </ul>
 
 <p>
 A match pattern of "http://*/" allows HTTP access to all reachable domains.
 Note that here,
-match patterns are similar to <a href="match_patterns.html">content script
+match patterns are similar to <a href="match_patterns">content script
 match patterns</a>,
 but any path information following the host is ignored.</p>
 
 <p>Also note that access is granted both by host and by scheme. If an extension
 wants both secure and non-secure HTTP access to a given host or set
 of hosts, it must declare the permissions separately:</p>
 
 <pre data-filename="manifest.json">
 "permissions": [
   "http://www.google.com/",
@@ skipping 62 matching lines @@
 Additionally, be especially careful of resources retrieved via HTTP.  If your
 extension is used on a hostile network, an network attacker (aka a <a
 href="http://en.wikipedia.org/wiki/Man-in-the-middle_attack">"man-in-the-middle"</a>)
 could modify the response and, potentially, attack your extension.  Instead,
 prefer HTTPS whenever possible.
 </p>
 
 <h3 id="interaction-with-csp">Interaction with Content Security Policy</h3>
 
 <p>
-If you modify the default <a href="contentSecurityPolicy.html">Content
+If you modify the default <a href="contentSecurityPolicy">Content
 Security Policy</a> for apps or extensions by adding a
 <code>content_security_policy</code> attribute to your manifest, you'll need to
 ensure that any hosts to which you'd like to connect are allowed. While the
 default policy doesn't restrict connections to hosts, be careful when explicitly
 adding either the <code>connect-src</code> or <code>default-src</code>
 directives.
 </p>