Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/sencha_framework.html
diff --git a/chrome/common/extensions/docs/templates/articles/sencha_framework.html b/chrome/common/extensions/docs/templates/articles/sencha_framework.html
index 7765e2e5ec7885cfde210ed151cedf06f9048514..84211508fae67ace37a28d336fc0d83c49314739 100644
--- a/chrome/common/extensions/docs/templates/articles/sencha_framework.html
+++ b/chrome/common/extensions/docs/templates/articles/sencha_framework.html
@@ -25,9 +25,9 @@ to build a media player app using Sencha Ext JS:
 
 <ul>
   <li>Create manifest, <code>manifest.json</code>.</li>
-  <li>Create <a href="app_lifecycle.html#eventpage">event page</a>,
+  <li>Create <a href="app_lifecycle#eventpage">event page</a>,
     <code>background.js</code>.</li>
-  <li><a href="app_external.html#sandboxing">Sandbox</a> app's logic.</li>
+  <li><a href="app_external#sandboxing">Sandbox</a> app's logic.</li>
   <li>Communicate between Chrome App and sandboxed files.</li>
   <li>Discover media servers.</li>
   <li>Explore and play media.</li>
@@ -38,7 +38,7 @@ to build a media player app using Sencha Ext JS:
 
 <p>
 All Chrome Apps require a
-<a href="manifest.html">manifest file</a>
+<a href="manifest">manifest file</a>
 which contains the information Chrome needs to launch apps.
 As indicated in the manifest,
 the media player app is "offline_enabled";
@@ -50,10 +50,10 @@ accessed and played regardless of connectivity.
 The "sandbox" field is used
 to sandbox the app's main logic in a unique origin.
 All sandboxed content is exempt from the Chrome App
-<a href="contentSecurityPolicy.html">Content Security Policy</a>,
+<a href="contentSecurityPolicy">Content Security Policy</a>,
 but cannot directly access the Chrome App APIs. 
 The manifest also includes the "socket" permission;
-the media player app uses the <a href="socket.html">socket API</a>
+the media player app uses the <a href="socket">socket API</a>
 to connect to a media server over the network.
 </p>
 
@@ -74,7 +74,7 @@ to connect to a media server over the network.
     ...
 
     "sandbox": {
-        "pages": ["sandbox.html"]
+        "pages": ["sandbox"]
     },
     "permissions": [
         "experimental",
@@ -96,7 +96,7 @@ to connect to a media server over the network.
 <p>
 All Chrome Apps require <code>background.js</code>
 to launch the application.
-The media player's main page, <code>index.html</code>,
+The media player's main page, <code>index</code>,
 opens in a window with the specified dimensions:
 </p>
 
@@ -107,7 +107,7 @@ chrome.app.runtime.onLaunched.addListener(function(launchData) {
         height: 700
     };
 
-    chrome.app.window.create('index.html', opt, function (win) {
+    chrome.app.window.create('index', opt, function (win) {
         win.launchData = launchData;
     });
 
@@ -117,20 +117,20 @@ chrome.app.runtime.onLaunched.addListener(function(launchData) {
 <h2 id="three">Sandbox app's logic</h2>
 
 <p>Chrome Apps run in a controlled environment
-that enforces a strict <a href="contentSecurityPolicy.html">Content Security Policy (CSP)</a>.
+that enforces a strict <a href="contentSecurityPolicy">Content Security Policy (CSP)</a>.
 The media player app needs some higher privileges to render the Ext JS components.
 To comply with CSP and execute the app logic,
-the app's main page, <code>index.html</code>, creates an iframe
+the app's main page, <code>index</code>, creates an iframe
 that acts as a sandbox environment:
 
-<pre data-filename="index.html">
-&lt;iframe id="sandbox-frame" sandbox="allow-scripts" src="sandbox.html">&lt;/iframe>
+<pre data-filename="index">
+&lt;iframe id="sandbox-frame" sandbox="allow-scripts" src="sandbox">&lt;/iframe>
 </pre>
 
-<p>The iframe points to <a href="https://github.com/GoogleChrome/sencha-video-player-app/blob/master/sandbox.html">sandbox.html</a> which includes the files required for the Ext JS application:
+<p>The iframe points to <a href="https://github.com/GoogleChrome/sencha-video-player-app/blob/master/sandbox">sandbox</a> which includes the files required for the Ext JS application:
 </p>
 
-<pre data-filename="sandbox.html">
+<pre data-filename="sandbox">
 &lt;html>
 &lt;head>
     &lt;link rel="stylesheet" type="text/css" href="resources/css/app.css" />'
@@ -144,7 +144,7 @@ that acts as a sandbox environment:
 </pre>
 
 <p>
-The <a href="http://senchaprosvcs.github.com/GooglePlayer/docs/output/source/app.html#VP-Application">app.js</a> script executes all the Ext JS code and renders the media player views.
+The <a href="http://senchaprosvcs.github.com/GooglePlayer/docs/output/source/app#VP-Application">app.js</a> script executes all the Ext JS code and renders the media player views.
 Since this script is sandboxed, it cannot directly access the Chrome App APIs.
 Communication between <code>app.js</code> and non-sandboxed files is done using the
 <a href="https://developer.mozilla.org/en-US/docs/DOM/window.postMessage">HTML5 Post Message API</a>.
@@ -253,7 +253,7 @@ calls <a href="https://github.com/GoogleChrome/sencha-video-player-app/blob/mast
 
 <p>
 The <code>Upnp library</code> uses the Chrome App
-<a href="app_network.html">socket API</a>
+<a href="app_network">socket API</a>
 to connect the media player app with any discovered media servers
 and receive media data from the media server.
 <code>Upnp.js</code> also uses