Remove .html extension from links

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

 <meta name="doc-family" content="apps">
 <h1>Chrome Apps Architecture</h1>
 
 
 <p>
 Chrome Apps integrate closely with a user’s operating system.
 They are designed to be run outside of a browser tab,
 to run robustly in offline and poor connectivity scenarios and
 to have far more powerful capabilities than are available
 in a typical web browsing environment.
@@ skipping 56 matching lines @@
 <p>
 
 <p>
 <iframe title="YouTube video player" width="610" height="380" src="//www.youtube.com/embed/yr1jgREbH8U" frameborder="0" allowfullscreen></iframe>
 </p>
 
 <h3 id="lifecycle">App lifecycle at a glance</h3>
 
 <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>
 
 <br>
 
 <table class="simple">
   <tr>
     <th scope="col"> Stage </th>
     <th scope="col"> Summary </th>
   </tr>
   <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>
     <td>Startup</td>
     <td>The event page is loaded,
       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.
     </td>
   </tr>
   <tr>
     <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>
     <td>Update</td>
     <td>Apps can be updated at any time;
       however, the code that a Chrome App is running
       cannot change during a startup/termination cycle.</td>
   </tr>
   <tr>
     <td>Uninstallation</td>
     <td>User can actively uninstall apps.
         When uninstalled, no executing code or
         private data is left behind.</td>
   </tr>
 </table>
 
 <h2 id="security">Security model</h2>
 
 <p>
 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
 and protecting users against man-in-the-middle attacks.
 </p>
 
 <p>
 Loading the Chrome App main page locally provides a place
 to enforce stricter security than the web.
 Like Chrome extensions,
@@ skipping 10 matching lines @@
 <p>
 Chrome Apps reuse Chrome extension process isolation,
 and take this a step further by isolating storage and external content.
 Each app has its own private storage area
 and can’t access the storage of another app
 or personal data (such as cookies) for websites that you use in your browser.
 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>
 
 <p>
 <iframe title="YouTube video player" width="610" height="380" src="//www.youtube.com/embed/EDtiWN42lHs" frameborder="0" allowfullscreen></iframe>
 </p>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>