Remove .html extension from links

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

 <h1>Tutorial: Google Analytics</h1>
 
 
 <p>
   This tutorial demonstrates using Google Analytics to track the usage of your
   extension. If you are developing a platform app, see <a
-  href="/apps/analytics.html">Analytics for Apps</a> since apps have different
+  href="/apps/analytics">Analytics for Apps</a> since apps have different
   restrictions from extensions.
 </p>
 
 <h2 id="toc-requirements">Requirements</h2>
 <p>
   This tutorial expects that you have some familiarity writing extensions for
   Google Chrome.  If you need information on how to write an extension, please
-  read the <a href="getstarted.html">Getting Started tutorial</a>.
+  read the <a href="getstarted">Getting Started tutorial</a>.
 </p>
 
 <p>
   You will also need a <a href="http://www.google.com/analytics">Google
   Analytics account</a> set up to track your extension. Note that when setting
   up the account, you can use any value in the Website's URL field, as your
   extension will not have an URL of its own.
 </p>
 
 <p style="text-align: center">
   <img src="{{static}}/images/tut_analytics/screenshot01.png"
        style="width:400px;height:82px;"
        alt="The analytics setup with info for a chrome extension filled out." />
 </p>
 
 <h2 id="toc-installing">Installing the tracking code</h2>
 
 <p>
   The standard Google Analytics tracking code snippet fetches a file named
   <code>ga.js</code> from an SSL protected URL if the current page
   was loaded using the <code>https://</code> protocol.  <strong>Chrome
   extensions and applications may <em>only</em> use the SSL-protected version of
   <code>ga.js</code></strong>. Loading <code>ga.js</code> over insecure HTTP is
-  disallowed by Chrome's default <a href="contentSecurityPolicy.html">Content
+  disallowed by Chrome's default <a href="contentSecurityPolicy">Content
   Security Policy</a>. This, plus the fact that Chrome extensions are hosted
   under the <code>chrome-extension://</code> schema, requires a slight
   modification to the usual tracking snippet to pull <code>ga.js</code> directly
   from <code>https://ssl.google-analytics.com/ga.js</code> instead of the
   default location.
 </p>
 
 <p>
   Below is a modified snippet for the
-  <a href="http://code.google.com/apis/analytics/docs/tracking/asyncTracking.html">asynchronous
+  <a href="http://code.google.com/apis/analytics/docs/tracking/asyncTracking">asynchronous
   tracking API</a> (the modified line is bolded):
 </p>
 
 <pre data-filename="asyncTracking.js">
 (function() {
   var ga = document.createElement('script'); ga.type = 'text/javascript'; ga.async = true;
   <strong>ga.src = 'https://ssl.google-analytics.com/ga.js';</strong>
   var s = document.getElementsByTagName('script')[0]; s.parentNode.insertBefore(ga, s);
 })();
 </pre>
 
 <p>
   You'll also need to ensure that your extension has access to load the resource
   by relaxing the default content security policy. The policy definition in your
-  <a href="manifest.html"><code>manifest.json</code></a> might look like:
+  <a href="manifest"><code>manifest.json</code></a> might look like:
 </p>
 
 <pre data-filename="manifest.json">
 {
   ...,
   "content_security_policy": "script-src 'self' https://ssl.google-analytics.com; object-src 'self'",
   ...
 }
 </pre>
 
 <p>
-  Here is a popup page (<code>popup.html</code>) which loads the asynchronous
+  Here is a popup page (<code>popup</code>) which loads the asynchronous
   tracking code via an external JavaScript file (<code>popup.js</code>) and
   tracks a single page view:
 </p>
 
-<pre data-filename="popup.html">
+<pre data-filename="popup">
 &lt;!DOCTYPE html>
 &lt;html>
  &lt;head>
    ...
   &lt;script src="popup.js">&lt;/script>
  &lt;/head>
  &lt;body>
    ...
  &lt;/body>
 &lt;/html>
@@ skipping 37 matching lines @@
        style="width:300px;height:119px;"
        alt="Analytics view of the top content for a site." />
 </p>
 
 <h2 id="toc-debugging">Monitoring analytics requests</h2>
 
 <p>
   To ensure that tracking data from your extension is being sent to Google
   Analytics, you can inspect the pages of your extension in the
   Developer Tools window (see the
-  <a href="tut_debugging.html">debugging tutorial</a> for more information).
+  <a href="tut_debugging">debugging tutorial</a> for more information).
   As the following figure shows, you should see requests for a file named
   <strong>__utm.gif</strong> if everything is set up correctly.
 </p>
 
 <p style="text-align: center">
   <img src="{{static}}/images/tut_analytics/screenshot04.png"
        style="width:683px;height:418px;"
        alt="Developer Tools window showing the __utm.gif request" />
 </p>
 
@@ skipping 59 matching lines @@
 <h2 id="toc-samplecode">Sample code</h2>
 
 <p>
   A sample extension that uses these techniques is
   available in the Chromium source tree:
 </p>
 
 <blockquote>
   <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/tutorials/analytics/">.../examples/tutorials/analytics/</a>
 </blockquote>