Remove .html extension from links

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

 <h1>Frequently Asked Questions</h1>
 
 
 <!--  -->
 
 <p>
 If you don't find an answer to your question here,
 try the
-<a href="http://code.google.com/chrome/webstore/faq.html">Chrome Web Store FAQ</a>, the
+<a href="http://code.google.com/chrome/webstore/faq">Chrome Web Store FAQ</a>, the
 <a href="http://stackoverflow.com/questions/tagged/google-chrome-extension">[google-chrome-extension] tag on Stack Overflow</a>, the
 <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions">group</a>, or the
 <a href="http://www.google.com/support/chrome_webstore/">store help</a>.
 </p>
 
 <div id="faq-TOC">
   <h4 id="general">General</h4>
   <ul>
     <li><a href="#faq-gen-01">What are Google Chrome Extensions?</a></li>
 {{^is_apps}}
@@ skipping 62 matching lines @@
   <p>
   Click the Chrome menu icon
   <img src="{{static}}/images/hotdogmenu.png" height="29" width="29" alt=""
     class="nomargin" />
   and select <b>Extensions</b> from the <b>Tools</b> menu.
   Ensure that the "Developer mode" checkbox in the top right-hand corner
   is checked.
   Now you can reload extensions,
   load an unpacked directory of files as if it were a packaged extension,
   and more. For a complete tutorial, see
-  <a href="/extensions/getstarted.html">Getting Started</a>.
+  <a href="/extensions/getstarted">Getting Started</a>.
 </p>
 {{/is_apps}}
 
 <h3 id="faq-gen-02">What technologies are used to write extensions for Chrome?</h3>
 <p>
   Extensions are written using the same standard web
   technologies that developers use to create websites. HTML is used as a
   content markup language, CSS is used for styling, and JavaScript for
   scripting. Because Chrome supports HTML5 and CSS3, developers can
   use the latest open web technologies such as canvas and CSS animations in
   their extensions. Extensions also have access to several
-  <a href="/extensions/api_other.html">JavaScript APIs</a>
+  <a href="/extensions/api_other">JavaScript APIs</a>
   that help perform functions like JSON encoding and interacting with the
   browser.
 </p>
 
 
 <h3 id="faq-gen-03">Are extensions fetched from the web every time the browser is loaded?</h3>
 <p>
   Extensions are downloaded by the Chrome browser upon install, and
   are subsequently run off of the local disk in order to speed up
   performance. However, if a new version of the extension is pushed online,
@@ skipping 40 matching lines @@
   combination.  The rest of the information is metadata about when the releases
   were first pushed, as well as revision numbers associated with each build.
 </p>
 
 
 <h2 id="capabilities2">Capabilities</h2>
 
 <h3 id="faq-dev-02">Can extensions make cross-domain Ajax requests?</h3>
 <p>
   Yes. Extensions can make cross-domain requests.  See
-  <a href="/extensions/xhr.html">this page</a>
+  <a href="/extensions/xhr">this page</a>
   for more information.
 </p>
 
 <h3 id="faq-dev-03">Can extensions use 3rd party web services?</h3>
 <p>
   Yes. Extensions are capable of making cross-domain Ajax
   requests, so they can call remote APIs directly. APIs that provide data
   in JSON format are particularly easy to use.
 </p>
 
@@ skipping 20 matching lines @@
 <h3 id="faq-dev-04">Can extensions use OAuth?</h3>
 <p>
   Yes, there are extensions that use OAuth to access remote data
   APIs. Most developers find it convenient to use a
   <a href="http://unitedheroes.net/OAuthSimple/js/OAuthSimple.js">JavaScript OAuth library</a>
   in order to simplify the process of signing OAuth requests.
 </p>
 
 <h3 id="faq-dev-06">Can extensions load DLLs?</h3>
 <p>
-  Yes, using the <a href="npapi.html">NPAPI interface</a>.
+  Yes, using the <a href="npapi">NPAPI interface</a>.
   Because of the possibility for abuse, though, we will review your extension
   before hosting it in the Chrome Web Store.
 </p>
 
 <h3 id="faq-dev-05">Can extensions create UI outside of the rendered web page?</h3>
 <p>
   Yes, your extension may add buttons to the Chrome browser's user interface.
-  See <a href="browserAction.html">browser actions</a> and
-  <a href="pageAction.html">page actions</a> for more information.
+  See <a href="browserAction">browser actions</a> and
+  <a href="pageAction">page actions</a> for more information.
 </p>
 <p>
   An extension may also create popup notifications, which exist outside of the
-  browser window.  See the <a href="desktop_notifications.html">desktop
+  browser window.  See the <a href="desktop_notifications">desktop
     notifications</a> documentation for more details.
 </p>
 
 <h3 id="faq-interact-chrome">Can extensions listen to clicks on Chrome tabs and
   navigation buttons?</h3>
 <p>
   No.  Extensions are limited to listening to the events described in the <a
-    href="api_index.html">API documentation</a>.
+    href="api_index">API documentation</a>.
 </p>
 
 <h3 id="faq-dev-11">Can two extensions communicate with each other?</h3>
 <p>
   Yes, extensions may pass messages to other extensions. See the
-  <a href="messaging.html#external">message passing documentation</a>
+  <a href="messaging#external">message passing documentation</a>
   for more information.
 </p>
 
 {{^is_apps}}
 <h3 id="faq-dev-13">Can extensions use Google Analytics?</h3>
 <p>
   Yes, since extensions are built just like websites, they can use
   <a href="http://www.google.com/analytics/">Google Analytics</a> to track
   usage.  However, you must modify the tracking code to pull
   an HTTPS version of the Google Analytics library.  See
-  <a href="tut_analytics.html">this tutorial</a> for more information on doing
+  <a href="tut_analytics">this tutorial</a> for more information on doing
   this.
 </p>
 {{/is_apps}}
 
 {{^is_apps}}
 <h3 id="faq-dev-15">Can extensions modify chrome:// URLs?</h3>
 <p>
   No. The extensions APIs have been designed to minimize backwards
   compatibility issues that can arise when new versions of the browser are
   pushed. Allowing content scripts on <code>chrome://</code>
   URLs would mean that developers would begin to rely on the DOM, CSS, and
   JavaScript of these pages to stay the same.  In the best case, these pages
   could not be updated as quickly as they are being updated right now.
   In the worst case, it could mean that an update to one
   of these pages could cause an extension to break, causing key parts of the
   browser to stop working for users of that extension.
 </p>
 
 <p>
-  The reason that <a href="override.html">replacing the content</a>
+  The reason that <a href="override">replacing the content</a>
   hosted at these URLs entirely is
   allowed is because it forces an extension developer to implement all of the
   functionality they want without depending on the browser's internal implementation
   to stay the same.
 </p>
 {{/is_apps}}
 
 <h3 id="faq-open-popups">Can extensions open browser/page action popups without
   user interaction?</h3>
 <p>
@@ skipping 33 matching lines @@
 
 <h3 id="faq-dev-09">How much data can I store in localStorage?</h3>
 <p>
   Extensions can store up to 5MB of data in localStorage.
 </p>
 
 {{^is_apps}}
 <h3 id="faq-dev-10">How do I create an options menu for my application?</h3>
 <p>
   You can let users set options for your extension by creating an
-  <a href="/extensions/options.html">options page</a>,
+  <a href="/extensions/options">options page</a>,
   which is a simple HTML page that will be loaded when a user clicks the
   "options" button for your extension. This page can read and write settings
   to localStorage, or even send options to a web server so that they can be
   persisted across browsers.
 </p>
 {{/is_apps}}
 
 <h3 id="faq-dev-12">What debugging tools are available to extension developers?</h3>
 <p>
   Chrome's built-in developer tools can be used to debug extensions
   as well as web pages. See this
-  <a href="/extensions/tut_debugging.html ">tutorial on debugging extensions</a>
+  <a href="/extensions/tut_debugging ">tutorial on debugging extensions</a>
   for more information.
 </p>
 
 <h3 id="faq-dev-16">Why do wildcard matches not work for top level domains
   (TLDs)?</h3>
 <p>
   You cannot use wildcard match patterns like <code>http://google.*/*</code>
   to match TLDs (like <code>http://google.es</code> and
   <code>http://google.fr</code>) due to the
   complexity of actually restricting such a match to only the desired domains.
@@ skipping 10 matching lines @@
   privileges.
 </p>
 <p>
   You should explicitly enumerate the TLDs that you wish to run
   your extension on.
 </p>
 
 <h3 id="faq-management">Why does the management API not fire events when my
   extension is installed/uninstalled?</h3>
 <p>
-  The <a href="management.html">management API</a> was intended to help create
+  The <a href="management">management API</a> was intended to help create
   new tab page replacement extensions.  It was not intended to fire
   install/uninstall events for the current extension.
 </p>
 
 <h3 id="faq-firstrun">How can an extension determine whether it is running for
   the first time?</h3>
 <p>
   You can listen to the
   $(ref:runtime.onInstalled)
   event. See <a href="#faq-lifecycle-events">this FAQ entry</a>.
@@ skipping 110 matching lines @@
     <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">
     discussion group</a> with a link back to your request.
   </li>
   <li>
     If you originally reported your request on the discussion group and were
     directed to this FAQ entry, reply to your original thread with a link
     to the ticket you starred or opened.  This will make it easier for others
     with the same request to find the correct ticket.
   </li>
 </ol>