Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/app_architecture.html
diff --git a/chrome/common/extensions/docs/templates/articles/app_architecture.html b/chrome/common/extensions/docs/templates/articles/app_architecture.html
index 1dc2bdeacbf9aaa83f49b46766611081c329ba51..c1016ff708e58cadbafa78a9ebadd4949486f360 100644
--- a/chrome/common/extensions/docs/templates/articles/app_architecture.html
+++ b/chrome/common/extensions/docs/templates/articles/app_architecture.html
@@ -74,7 +74,7 @@ There can only be one “event page” for a Chrome App.
 
 <p>
 For detailed instructions on how to use the programming model,
-see <a href="app_lifecycle.html">Manage App Lifecycle</a>.
+see <a href="app_lifecycle">Manage App Lifecycle</a>.
 Here's a brief summary of the Chrome App lifecyle
 to get you started:
 </p>
@@ -89,7 +89,7 @@ to get you started:
   <tr>
     <td>Installation</td>
     <td>User chooses to install the app and explicitly accepts the
-    	<a href="declare_permissions.html">permissions</a>.
+    	<a href="declare_permissions">permissions</a>.
     </td>
   </tr>
   <tr>
@@ -98,7 +98,7 @@ to get you started:
       the 'launch' event fires,
       and app pages open in windows.
       You 
-      <a href="app_lifecycle.html#eventpage">create the windows</a>
+      <a href="app_lifecycle#eventpage">create the windows</a>
       that your app requires,
       how they look, and how they communicate
       with the event page and with other windows.
@@ -108,7 +108,7 @@ to get you started:
     <td>Termination</td>
     <td>User can terminate apps at any time
       and app can be quickly restored to previous state.
-      <a href="app_lifecycle.html#local_settings">Stashing data</a>
+      <a href="app_lifecycle#local_settings">Stashing data</a>
     	protects against data loss.</td>
   </tr>
   <tr>
@@ -131,7 +131,7 @@ to get you started:
 The Chrome Apps security model protects users
 by ensuring their information is managed
 in a safe and secure manner.
-<a href="contentSecurityPolicy.html">Comply with CSP</a>
+<a href="contentSecurityPolicy">Comply with CSP</a>
 includes detailed information on how to comply with content security policy.
 This policy blocks dangerous scripting
 reducing cross-site scripting bugs
@@ -162,7 +162,7 @@ All external processes are isolated from the app.
 Since iframes run in the same process as the surrounding page,
 they can only be used to load other app pages.
 You can use the <code>object</code> tag to
-<a href="app_external.html">embed external content</a>;
+<a href="app_external">embed external content</a>;
 this content runs in a separate process from the app.
 </p>