Remove .html extension from links

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

 <meta name="doc-family" content="apps">
 <h1>Build Apps with AngularJS</h1>
 <!--Article written by Eric Bidelman-->
 <p>
 This guide gets you started building Chrome Apps
 with the <a href="http://angularjs.org/">AngularJS</a> MVC framework.
 To illustrate Angular in action,
 we'll be referencing an actual app built using the framework,
 the Google Drive Uploader.
 The <a href="https://github.com/GoogleChrome/chrome-app-samples/tree/master/gdrive">source code</a>
@@ skipping 15 matching lines @@
 <a href="http://www.html5rocks.com/en/tutorials/dnd/basics/">HTML Drag and Drop APIs</a>.
 It's a great example of building an app which talks
 to one of <a href="https://developers.google.com/apis-explorer/#p/">Google's APIs</a>;
 in this case, the Google Drive API.
 </p>
 
 <p class="note">
 <strong>Note: </strong>
 You can also build apps which talk to 3rd party APIs/services
 that are OAuth2-enabled.
-See <a href="app_identity.html#non">non-Google Account authentication</a>.
+See <a href="app_identity#non">non-Google Account authentication</a>.
 </p>
 
 <p>
 The Uploader uses OAuth2 to access the user's data. The
-<a href="identity.html">chrome.identity API</a>
+<a href="identityhtml">chrome.identity API</a>
 handles fetching an OAuth token for the logged-in user,
 so the hard work is done for us!
 Once we have a long-lived access token,
 the apps uses the
 <a href="https://developers.google.com/drive/get-started">Google Drive API</a>
 to access the user's data.
 </p>
 
 <p>
 Key features this app uses:
 </p>
 
 <ul>
     <li>AngularJS's autodetection for
-        <a href="contentSecurityPolicy.html">CSP</a></li>
+        <a href="contentSecurityPolicyhtml">CSP</a></li>
     <li>Render a list of files fetched from the
         <a href="https://developers.google.com/drive/get-started">Google Drive API</a></li>
     <li><a href="http://www.html5rocks.com/en/tutorials/file/filesystem/">HTML5 Filesystem API</a>
         to store file icons offline</li>
     <li><a href="http://www.html5rocks.com/en/tutorials/dnd/basics/">HTML5 Drag and Drop</a>
         for importing/uploading new files from the desktop</li>
     <li>XHR2 to load images, cross-domain</li>
-    <li><a href="app_identity.html">chrome.identity API</a>
+    <li><a href="app_identityhtml">chrome.identity API</a>
         for OAuth authorization</li>
     <li>Chromeless frames to define the app's own navbar look and feel</li>
 </ul>
 
 <h2 id="second">Creating the manifest</h2>
 
 <p>
 All Chrome Apps require a <code>manifest.json</code> file
 which contains the information Chrome needs to launch the app.
 The manifest contains relevant metadata and
@@ skipping 26 matching lines @@
 }
 </pre>
 
 <p>
 The most important parts of this manifest are the "oauth2" and "permissions" sections.
 </p>
 
 <p>
 The "oauth2" section defines the required parameters by OAuth2 to do its magic.
 To create a "client_id", follow the instructions in
-<a href="app_identity.html#client_id">Get your client id</a>.
+<a href="app_identityhtml#client_id">Get your client id</a>.
 The "scopes" list the authorization scopes
 that the OAuth token will be valid for (for example, the APIs the app wants to access).
 </p>
 
 <p>
 The "permissions" section includes URLs that the app will access via XHR2.
 The URL prefixes are required in order for Chrome
 to know which cross-domain requests to allow.
 </p>
 
@@ skipping 201 matching lines @@
     &lt;/li>
   &lt;/ul>
 &lt;/section>
 </pre>
 
 <h3 id="csp">A word on Content Security Policy</h3>
 
 <p>
 Unlike many other JS MVC frameworks,
 Angular v1.1.0+ requires no tweaks to work within a strict
-<a href="contentSecurityPolicy.html">CSP</a>.
+<a href="contentSecurityPolicyhtml">CSP</a>.
 It just works, out of the box!
 </p>
 
 <p>
 However, if you're using an older version
 of Angular between v1.0.1 and v1.1.0,
 you'll need tell Angular to run in a "content security mode".
 This is done by including the
 <a href="http://docs.angularjs.org/api/ng.directive:ngCsp">ngCsp</a>
 directive alongside <a href="http://docs.angularjs.org/api/ng.directive:ngApp">ngApp</a>:
@@ skipping 406 matching lines @@
         $scope.fetchDocs();
       });
     });
   });
 
   return gdocs;
 });
 </pre>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>