Remove .html extension from links

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

 <h1>Tutorial: OAuth</h1>
 
 
 <p>
 <a href="http://oauth.net/">OAuth</a> is an open protocol that aims to standardize the way desktop and web applications access a user's private data. OAuth provides a mechanism for users to grant access to private data without sharing their private credentials (username/password). Many sites have started enabling APIs to use OAuth because of its security and standard set of libraries.
 </p>
 <p>
 This tutorial will walk you through the necessary steps for creating a Google Chrome Extension that uses OAuth to access an API. It leverages a library that you can reuse in your extensions.
 </p>
 <p>
 This tutorial uses the <a href="http://code.google.com/apis/documents/">Google Documents List Data API</a> as an example OAuth-enabled API endpoint.
 </p>
 
 <h2 id="requirements">Requirements</h2>
 
 <p>
-This tutorial expects that you have some experience writing extensions for Google Chrome and some familiarity with the <a href="http://code.google.com/apis/accounts/docs/OAuth.html">3-legged OAuth</a> flow. Although you don’t need a background in the <a href="http://code.google.com/apis/documents/">Google Documents List Data API</a> (or the other <a href="http://code.google.com/apis/gdata/">Google Data APIs</a> for that matter), having an understanding of the protocol may be helpful.
+This tutorial expects that you have some experience writing extensions for Google Chrome and some familiarity with the <a href="http://code.google.com/apis/accounts/docs/OAuth">3-legged OAuth</a> flow. Although you don’t need a background in the <a href="http://code.google.com/apis/documents/">Google Documents List Data API</a> (or the other <a href="http://code.google.com/apis/gdata/">Google Data APIs</a> for that matter), having an understanding of the protocol may be helpful.
 </p>
 
 <h2 id="getting-started">Getting started</h2>
 
 <p>
 First, copy the four library files from the Chromium source tree at <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/extensions/oauth_contacts/">.../examples/extensions/oauth_contacts/</a>:
 </p>
 <ul>
-<li><strong><a href="examples/extensions/oauth_contacts/chrome_ex_oauth.html" download="chrome_ex_oauth.html">chrome_ex_oauth.html</a></strong> - interstitial page for the oauth_callback URL</li>
+<li><strong><a href="examples/extensions/oauth_contacts/chrome_ex_oauth" download="chrome_ex_oauth">chrome_ex_oauth</a></strong> - interstitial page for the oauth_callback URL</li>
 <li><strong><a href="examples/extensions/oauth_contacts/chrome_ex_oauth.js" download="chrome_ex_oauth.js">chrome_ex_oauth.js</a></strong> - core OAuth library</li>
 <li><strong><a href="examples/extensions/oauth_contacts/chrome_ex_oauthsimple.js" download="chrome_ex_oauthsimple.js">chrome_ex_oauthsimple.js</a></strong> - helpful wrapper for chrome_ex_oauth.js</li>
 <li><strong><a href="examples/extensions/oauth_contacts/onload.js" download="onload.js">onload.js</a></strong> -
-initializes chrome_ex_oauth.html and redirects the page if needed to start the OAuth flow</li>
+initializes chrome_ex_oauth and redirects the page if needed to start the OAuth flow</li>
 </ul>
 
 <p>Place the four library files in the root of your extension directory (or wherever your JavaScript is stored). Then include the .js files in your background page in the following order:</p>
 
 <pre>
 &lt;script type="text/javascript" src="chrome_ex_oauthsimple.js"&gt;&lt;/script&gt;
 &lt;script type="text/javascript" src="chrome_ex_oauth.js"&gt;&lt;/script&gt;
 &lt;script type="text/javascript" src="onload.js"&gt;&lt;/script&gt;
 </pre>
 
 <p>Your background page will manage the OAuth flow.</p>
 
 <h2 id="oauth-dance">The OAuth dance in an extension</h2>
 
 <p>
 If you are familiar with the OAuth protocol, you'll recall that the OAuth dance consists of three steps:
 </p>
 
 <ol>
 <li>fetching an initial request token</li>
 <li>having the user authorize the request token</li>
 <li>fetching an access token</li>
 </ol>
 
 <p>In the context of an extension, this flow gets a bit tricky. Namely, there is no established consumer key/secret between the service provider and the application. That is, there is no web application URL for the user to be redirected to after the approval process.
 </p>
 
 <p>
-Luckily, Google and a few other companies have been working on an <a href="http://code.google.com/apis/accounts/docs/OAuthForInstalledApps.html">OAuth for installed applications</a> solution that you can use from an extension environment. In the installed applications OAuth dance, the consumer key/secret are ‘anonymous’/’anonymous’ and you provide an <em>application name</em> for the user to grant access to (instead of an application URL). The end result is the same: your background page requests the initial token, opens a new tab to the approval page, and finally makes the asynchronous call for the access token.
+Luckily, Google and a few other companies have been working on an <a href="http://code.google.com/apis/accounts/docs/OAuthForInstalledApps">OAuth for installed applications</a> solution that you can use from an extension environment. In the installed applications OAuth dance, the consumer key/secret are ‘anonymous’/’anonymous’ and you provide an <em>application name</em> for the user to grant access to (instead of an application URL). The end result is the same: your background page requests the initial token, opens a new tab to the approval page, and finally makes the asynchronous call for the access token.
 </p>
 
 <h3 id="set-code">Setup code</h3>
 
 <p>To initialize the library, create a <code>ChromeExOAuth</code> object in the background page:</p>
 
 <pre>
 var oauth = ChromeExOAuth.initBackgroundPage({
   'request_url': &lt;OAuth request URL&gt;,
   'authorize_url': &lt;OAuth authorize URL&gt;,
@@ skipping 15 matching lines @@
   'consumer_key': 'anonymous',
   'consumer_secret': 'anonymous',
   'scope': 'https://docs.google.com/feeds/',
   'app_name': 'My Google Docs Extension'
 });
 </pre>
 
 <p>
 To use the OAuth library,
 you must declare the "tabs" permision in the
-<a href="manifest.html">extension manifest</a>.
+<a href="manifest">extension manifest</a>.
 You must also declare the sites you are using
 including the request URL, the authorize URL, access URL,
 and, if necessary, the scope URL.
 For example:
 </p>
 
 <pre data-filename="manifest.json">
 "permissions": [ "tabs", "https://docs.google.com/feeds/*",
   "https://www.google.com/accounts/OAuthGetRequestToken",
   "https://www.google.com/accounts/OAuthAuthorizeToken",
@@ skipping 103 matching lines @@
 <h2 id="sample-code">Sample code</h2>
 
 <p>
 Sample extensions that use these techniques are available in the Chromium source tree:
 </p>
 
 <ul>
 <li><a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/extensions/gdocs/">.../examples/extensions/gdocs/</a></li>
 <li><a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/extensions/oauth_contacts/">.../examples/extensions/oauth_contacts/</a></li>
 </ul>