Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/angular_framework.html
diff --git a/chrome/common/extensions/docs/templates/articles/angular_framework.html b/chrome/common/extensions/docs/templates/articles/angular_framework.html
index ff61c1ba3a42cacf2348d9e7563f5338dda37c9e..1b564a275307e497505e1b5df7d23473c20ca719 100644
--- a/chrome/common/extensions/docs/templates/articles/angular_framework.html
+++ b/chrome/common/extensions/docs/templates/articles/angular_framework.html
@@ -33,12 +33,12 @@ in this case, the Google Drive API.
 <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="identity">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,
@@ -53,7 +53,7 @@ Key features this app uses:
 
 <ul>
     <li>AngularJS's autodetection for
-        <a href="contentSecurityPolicy.html">CSP</a></li>
+        <a href="contentSecurityPolicy">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>
@@ -61,7 +61,7 @@ Key features this app uses:
     <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_identity">chrome.identity API</a>
         for OAuth authorization</li>
     <li>Chromeless frames to define the app's own navbar look and feel</li>
 </ul>
@@ -108,7 +108,7 @@ The most important parts of this manifest are the "oauth2" and "permissions" sec
 <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_identity#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>
@@ -137,7 +137,7 @@ so the content doesn't become too crunched:
 
 <pre data-filename="background.js">
 chrome.app.runtime.onLaunched.addListener(function(launchData) {
-  chrome.app.window.create('../main.html', {
+  chrome.app.window.create('../main', {
     id: "GDriveExample",
     bounds: {
       width: 500,
@@ -162,7 +162,7 @@ By default, windows render with the OS's default close/expand/minimize bar:
 
 <p>
 The Uploader uses <code>frame: 'none'</code> to render the window as a "blank slate"
-and creates a custom close button in <code>main.html</code>:
+and creates a custom close button in <code>main</code>:
 </p>
 
 <img src="{{static}}/images/customframe.png"
@@ -191,7 +191,7 @@ nav:hover #close-button {
 }
 &lt;/style>
 </pre>
-<pre data-filename="main.html">
+<pre data-filename="main">
 &lt;button class="btn" id="close-button" title="Close">x&lt;/button>
 </pre>
 
@@ -215,7 +215,7 @@ The View is the easiest, so let's start there.
 <h3 id="view">Creating the view</h3>
 
 <p>
-<a href="https://github.com/GoogleChrome/chrome-app-samples/blob/master/gdrive/main.html">main.html</a>
+<a href="https://github.com/GoogleChrome/chrome-app-samples/blob/master/gdrive/main">main</a>
 is the "V" in MVC; where we define HTML templates to render data into.
 In Angular, templates are simple blocks of HTML with some special sauce.
 </p>
@@ -226,7 +226,7 @@ For that, a simple &lt;ul> list makes sense.
 The Angular bits are highlighted in bold: 
 </p>
 
-<pre data-filename="main.html">
+<pre data-filename="main">
 &lt;ul>
   &lt;li <strong>data-ng-repeat="doc in docs"</strong>>
     &lt;img data-ng-src=<strong>"&#123;{doc.icon}&#125;"</strong>> &lt;a href=<strong>"&#123;{doc.alternateLink}&#125;"</strong>><strong>&#123;{doc.title}&#125;</strong>&lt;/a>
@@ -259,7 +259,7 @@ For that, we use the
 directive to tell the <code>DocsController</code> to have reign over the template &lt;body&gt;:
 </p>
 
-<pre data-filename="main.html">
+<pre data-filename="main">
 &lt;body <strong>data-ng-controller="DocsController"</strong>>
 &lt;section id="main">
   &lt;ul>
@@ -285,7 +285,7 @@ The typical way to do that is include the
 directive all the way up on &lt;html>:
 </p>
 
-<pre data-filename="main.html">
+<pre data-filename="main">
 &lt;html <strong>data-ng-app="gDriveApp"</strong>>
 </pre>
 
@@ -299,10 +299,10 @@ on the topmost element makes the entire page Angular-ready.
 </p>
 
 <p>
-The final product for <code>main.html</code> looks something like this:
+The final product for <code>main</code> looks something like this:
 </p>
 
-<pre data-filename="main.html">
+<pre data-filename="main">
 &lt;html <strong>data-ng-app="gDriveApp"</strong>>
 &lt;head>
   …
@@ -330,7 +330,7 @@ The final product for <code>main.html</code> looks something like this:
 <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="contentSecurityPolicy">CSP</a>.
 It just works, out of the box!
 </p>
 
@@ -343,7 +343,7 @@ This is done by including the
 directive alongside <a href="http://docs.angularjs.org/api/ng.directive:ngApp">ngApp</a>:
 </p>
 
-<pre data-filename="main.html">
+<pre data-filename="main">
 &lt;html data-ng-app data-ng-csp>
 </pre>