Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/getstarted.html
diff --git a/chrome/common/extensions/docs/templates/articles/getstarted.html b/chrome/common/extensions/docs/templates/articles/getstarted.html
index 23e577b986e48d5dd5d05a625c0e9aa81e456d64..5174aedbe73f9b13da832f0db80915fec3e4653e 100644
--- a/chrome/common/extensions/docs/templates/articles/getstarted.html
+++ b/chrome/common/extensions/docs/templates/articles/getstarted.html
@@ -12,7 +12,7 @@
 
 <p>
   We'll do so by implementing a UI element we call a
-  <a href="browserAction.html">browser action</a>, which allows us to place a
+  <a href="browserAction">browser action</a>, which allows us to place a
   clickable icon right next to Chrome's Omnibox for easy access. Clicking that
   icon will open a popup window filled with kittenish goodness, which will look
   something like this:
@@ -60,7 +60,7 @@
   ],
   "browser_action": {
     "default_icon": "icon.png",
-    "default_popup": "popup.html"
+    "default_popup": "popup"
   }
 }
 </pre>
@@ -107,7 +107,7 @@
 <p>
   You probably noticed that <code>manifest.json</code> pointed at two resource
   files when defining the browser action: <code>icon.png</code> and
-  <code>popup.html</code>. Both resources must exist inside the extension
+  <code>popup</code>. Both resources must exist inside the extension
   package, so let's create them now:
 </p>
 
@@ -132,17 +132,17 @@
            width="165"
            height="200"
            alt="The popup's HTML will be rendered directly below the icon when clicked.">
-      <code>popup.html</code> will be rendered inside the popup window that's
+      <code>popup</code> will be rendered inside the popup window that's
       created in response to a user's click on the browser action. It's a
       standard HTML file, just like you're used to from web development, giving
       you more or less free reign over what the popup displays.
-      <a href="examples/tutorials/getstarted/popup.html" download="popup.html">
-        Download a copy of <code>popup.html</code> from our sample repository
+      <a href="examples/tutorials/getstarted/popup" download="popup">
+        Download a copy of <code>popup</code> from our sample repository
       </a>, and save it into
       the directory you're working in.
     </p>
     <p>
-      <code>popup.html</code> requires an additional JavaScript file in order to
+      <code>popup</code> requires an additional JavaScript file in order to
       do the work of grabbing kitten images from the web and loading them into
       the popup. To save you some effort, just
       <a href="examples/tutorials/getstarted/popup.js" download="popup.js">
@@ -156,7 +156,7 @@
   You should now have four files in your working directory:
   <a href="examples/tutorials/getstarted/icon.png" download="icon.png"><code>icon.png</code></a>,
   <a href="examples/tutorials/getstarted/manifest.json" download="manifest.json"><code>manifest.json</code></a>,
-  <a href="examples/tutorials/getstarted/popup.html" download="popup.html"><code>popup.html</code></a>,
+  <a href="examples/tutorials/getstarted/popup" download="popup"><code>popup</code></a>,
   <a href="examples/tutorials/getstarted/popup.js" download="popup.js"><code>popup.js</code></a>.
   The next step is to load those files into Chrome.
 </p>
@@ -253,7 +253,7 @@
 <ul>
   <li>
     <p>
-      The <a href="overview.html">Chrome Extension Overview</a> backs up a bit,
+      The <a href="overview">Chrome Extension Overview</a> backs up a bit,
       and fills in a lot of detail about extensions' architecture in general,
       and some specific concepts you'll want to be familiar with going forward.
       It's the best next step on your journey towards extension mastery.
@@ -263,7 +263,7 @@
     <p>
       No one writes perfect code on the first try, which means that you'll need
       to learn about the options available for debugging your creations. Our
-      <a href="tut_debugging.html">debugging tutorial</a> is perfect for that,
+      <a href="tut_debugging">debugging tutorial</a> is perfect for that,
       and is well worth carefully reading.
     </p>
   </li>
@@ -271,13 +271,13 @@
     <p>
       Chrome extensions have access to powerful APIs above and beyond what's
       available on the open web: browser actions are just the tip of the
-      iceburg. Our <a href="api_index.html">chrome.* APIs documentation</a> will
+      iceburg. Our <a href="api_index">chrome.* APIs documentation</a> will
       walk you through each API in turn.
     </p>
   </li>
   <li>
     <p>
-      Finally, the <a href="devguide.html">developer's guide</a> has dozens of
+      Finally, the <a href="devguide">developer's guide</a> has dozens of
       additional links to pieces of documentation you might be interested in.
     </p>
   </li>