Remove .html extension from links

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

Index: chrome/common/extensions/docs/templates/articles/tut_oauth.html
diff --git a/chrome/common/extensions/docs/templates/articles/tut_oauth.html b/chrome/common/extensions/docs/templates/articles/tut_oauth.html
index b58c49cdc89b0794edc06faaafb28ed965721223..a68ee420fd640e28e49b16dd853d06189cc8dd1c 100644
--- a/chrome/common/extensions/docs/templates/articles/tut_oauth.html
+++ b/chrome/common/extensions/docs/templates/articles/tut_oauth.html
@@ -14,7 +14,7 @@ This tutorial uses the <a href="http://code.google.com/apis/documents/">Google D
 <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>
@@ -23,11 +23,11 @@ This tutorial expects that you have some experience writing extensions for Googl
 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>
@@ -56,7 +56,7 @@ If you are familiar with the OAuth protocol, you'll recall that the OAuth dance
 </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>
@@ -92,7 +92,7 @@ var oauth = ChromeExOAuth.initBackgroundPage({
 <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.