Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/develop_apps.html
diff --git a/chrome/common/extensions/docs/templates/articles/develop_apps.html b/chrome/common/extensions/docs/templates/articles/develop_apps.html
index 3d0402e76c14a729527d14fbbe77d0c0f50f3324..8b58e052b6ae91c3ebf4d7b9eff3d39956282675 100644
--- a/chrome/common/extensions/docs/templates/articles/develop_apps.html
+++ b/chrome/common/extensions/docs/templates/articles/develop_apps.html
@@ -12,7 +12,7 @@ Please keep up to date with the API reference and documentation.
 <p class="caution">
 <b>Note:</b>
 If you've written packaged apps before,
-your <a href="/extensions/apps.html">legacy packaged apps</a>
+your <a href="/extensions/apps">legacy packaged apps</a>
 will still work the way they always have,
 but they won't have access to the new APIs.
 </p>
@@ -24,7 +24,7 @@ Chrome Apps and extensions share a common platform.
 They can access many of the same APIs and
 they have the same manifest and permissions format.
 If you're familiar with the
-<a href="/extensions/index.html">Chrome Extension docs</a>,
+<a href="/extensions/index">Chrome Extension docs</a>,
 then the Reference docs should seem familiar.
 Many of the reference docs are shared;
 we've filtered accessibility to docs that aren't.
@@ -34,11 +34,11 @@ we've filtered accessibility to docs that aren't.
 
 <ul>
   <li>Read the
-  <a href="about_apps.html">Getting Started</a> guide.</li>
+  <a href="about_apps">Getting Started</a> guide.</li>
   <li>Follow the
-  <a href="app_codelab.html">Todo App Codelab</a>.</li>
+  <a href="app_codelab">Todo App Codelab</a>.</li>
   <li>Check out the
-  <a href="api_index.html">Chrome JavaScript APIs</a>.</li>
+  <a href="api_index">Chrome JavaScript APIs</a>.</li>
   <li>Fork any and all
   <a href="https://github.com/GoogleChrome/chrome-app-samples">chrome-app-samples</a> and make something of your own.</li>
   <li>Watch the