Remove .html extension from links

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

 <h1>Getting Started: Building a Chrome Extension</h1>
 
 <p>
   Extensions allow you to add functionality to Chrome without diving deeply
   into native code. You can create new extensions for Chrome with those core
   technologies that you're already familiar with from web development: HTML,
   CSS, and JavaScript. If you've ever built a web page, you should feel right at
   home with extensions pretty quickly; we'll put that to the test right now by
   walking through the construction of a simple extension that will give you
   one-click access to pictures of kittens. Kittens!
 </p>
 
 <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:
 </p>
 
 <img src="{{static}}/images/gettingstarted-1.jpg"
      width="600"
      height="420"
      alt="Chrome, with an extension's popup open and displaying many kittens.">
 
@@ skipping 27 matching lines @@
 
   "name": "One-click Kittens",
   "description": "This extension demonstrates a browser action with kittens.",
   "version": "1.0",
 
   "permissions": [
     "https://secure.flickr.com/"
   ],
   "browser_action": {
     "default_icon": "icon.png",
-    "default_popup": "popup.html"
+    "default_popup": "popup"
   }
 }
 </pre>
 
 <p>
   Go ahead and save that data to a file named <code>manifest.json</code> in the
   directory you created, or
   <a href="examples/tutorials/getstarted/manifest.json" download="manifest.json">
     download a copy of <code>manifest.json</code> from our sample repository
   </a>.
@@ skipping 26 matching lines @@
   <code>https://secure.flickr.com/</code>, and declares that this extension
   implements a browser action, assigning it a default icon and popup in the
   process.
 </p>
 
 <h2 id="resources">Resources</h2>
 
 <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>
 
 <ul class="imaged">
   <li>
     <p>
       <img src="{{static}}/images/gettingstarted-icon.png"
            width="127"
            height="127"
            alt="The popup's icon will be displayed right next to the Omnibox.">
       <code>icon.png</code> will be displayed next to the Omnibox, waiting for
       user interaction. Download a copy of icon.png from our sample repository,
       <a href="examples/tutorials/getstarted/icon.png" download="icon.png">
         Download a copy of <code>icon.png</code> from our sample repository
       </a>, and save it into the directory you're working in. You could also
       create your own if you're so inclined; it's just a 19px-square PNG file.
     </p>
   </li>
   <li>
     <p>
       <img src="{{static}}/images/gettingstarted-popup.jpg"
            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">
         download a copy of <code>popup.js</code> from our sample repository
       </a>, and save it into the directory you're working in.
     </p>
   </li>
 </ul>
 
 <p>
   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>
 
 <h2 id="unpacked">Load the extension</h2>
 
 <p>
   Extensions that you download from the Chrome Web Store are packaged up as
   <code>.crx</code> files, which is great for distribution, but not so great for
   development. Recognizing this, Chrome gives you a quick way of loading up your
@@ skipping 76 matching lines @@
   You now know about the manifest file's central role in bringing things
   together, and you've mastered the basics of declaring a browser action, and
   rendering some kittens (or puppies!) in response to a user's click. That's a
   great start, and has hopefully gotten you interested enough to explore
   further. There's a lot more out there to play around with.
 </p>
 
 <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.
     </p>
   </li>
   <li>
     <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>
   <li>
     <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>
 </ul>