Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/apps.html
diff --git a/chrome/common/extensions/docs/templates/articles/apps.html b/chrome/common/extensions/docs/templates/articles/apps.html
index de1eaaf21315132cbca2ed90ba6b61cedec149ae..2d86e7f51e1deb18d8ec934f5f3445d2e101bcd7 100644
--- a/chrome/common/extensions/docs/templates/articles/apps.html
+++ b/chrome/common/extensions/docs/templates/articles/apps.html
@@ -7,7 +7,7 @@ All content in this doc refers to the legacy version of packaged apps.
 Your legacy packaged apps will still work,
 but you won't have access to any of the new APIs.
 Check out the new version of
-<a href="../apps/about_apps.html">Chrome Apps</a>;
+<a href="../apps/about_apps">Chrome Apps</a>;
 otherwise, you're missing out!
 </p>
 
@@ -26,8 +26,8 @@ that's bundled into a <code>.crx</code> file
 and can use Chrome extension features.
 You build a packaged app just like you build an extension,
 except that a packaged app can't include a
-<a href="browserAction.html">browser action</a> or
-<a href="pageAction.html">page action</a>.
+<a href="browserAction">browser action</a> or
+<a href="pageAction">page action</a>.
 Instead, a packaged app includes at least one HTML file
 within its <code>.crx</code> file
 that provides the app's user interface.
@@ -38,7 +38,7 @@ Packaged apps are a type of
 <a href="http://code.google.com/chrome/apps/">installable web app</a>&mdash;a
 web app that can be installed in Chrome.
 The other type of installable web app is a
-<a href="http://code.google.com/chrome/apps/docs/developers_guide.html">hosted app</a>,
+<a href="http://code.google.com/chrome/apps/docs/developers_guide">hosted app</a>,
 which is an ordinary web app with a bit of additional metadata.
 </p>
 
@@ -70,7 +70,7 @@ read these:
 
 <ul>
   <li> <a href="http://code.google.com/chrome/webstore/docs/choosing.html">Choosing an App Type</a> </li>
-  <li> <a href="http://code.google.com/chrome/apps/articles/thinking_in_web_apps.html">Thinking in Web Apps</a> </li>
+  <li> <a href="http://code.google.com/chrome/apps/articles/thinking_in_web_apps">Thinking in Web Apps</a> </li>

[mkearney1, 2014/05/14 19:56:06]

Keep .html here, especially since similar links have it. I wonder if these links
still work, on an side, as it's code.google.com.

   <li> <a href="http://code.google.com/chrome/webstore/articles/apps_vs_extensions.html">Extensions, Packaged Apps, and Hosted Apps in the Chrome Web Store</a> </li>
 </ul>
 
@@ -158,19 +158,19 @@ tabs that contain app's pages.
 They also should provide a 128x128 icon,
 but not a 48x48 icon.
 See the manifest documentation for the
-<a href="manifest/icons.html">"icons" field</a>
+<a href="manifest/icons">"icons" field</a>
 for more information.
 </p>
 
 <p>
 For further details on what a packaged app's manifest can contain, see the
-<a href="manifest.html">manifest documentation</a>.
+<a href="manifest">manifest documentation</a>.
 </p>
 
 <h2 id="next">What next?</h2>
 
 <p>
-Read the <a href="overview.html">Overview</a> to learn
+Read the <a href="overview">Overview</a> to learn
 basic concepts about extensions.
 </p>