Extension docs: Cleanup after there's only one version.

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

Index: chrome/common/extensions/docs/templates/articles/faq.html
diff --git a/chrome/common/extensions/docs/templates/articles/faq.html b/chrome/common/extensions/docs/templates/articles/faq.html
index fce26c9ba6066b533db6ed00c7ca5e6219cc4c2d..fb46764da781d009732020c5e8a972cffa039007 100644
--- a/chrome/common/extensions/docs/templates/articles/faq.html
+++ b/chrome/common/extensions/docs/templates/articles/faq.html
@@ -89,7 +89,7 @@ try the
   Now you can reload extensions,
   load an unpacked directory of files as if it were a packaged extension,
   and more. For a complete tutorial, see
-  <a href="http://code.google.com/chrome/extensions/getstarted.html">Getting Started</a>.
+  <a href="/extensions/getstarted.html">Getting Started</a>.
 </p>
 {{/is_apps}}
 
@@ -101,7 +101,7 @@ try the
   scripting. Because Chrome supports HTML5 and CSS3, developers can
   use the latest open web technologies such as canvas and CSS animations in
   their extensions. Extensions also have access to several
-  <a href="http://code.google.com/chrome/extensions/api_other.html">JavaScript APIs</a>
+  <a href="/extensions/api_other.html">JavaScript APIs</a>
   that help perform functions like JSON encoding and interacting with the
   browser.
 </p>
@@ -162,7 +162,7 @@ cros,beta,#.#.###.#,#.#.###.#,mm/dd/yy,mm/dd/yy,#####,#####,#####</pre>
 <h3 id="faq-dev-02">Can extensions make cross-domain Ajax requests?</h3>
 <p>
   Yes. Extensions can make cross-domain requests.  See
-  <a href="http://code.google.com/chrome/extensions/xhr.html">this page</a>
+  <a href="/extensions/xhr.html">this page</a>
   for more information.
 </p>
 
@@ -315,7 +315,7 @@ cros,beta,#.#.###.#,#.#.###.#,mm/dd/yy,mm/dd/yy,#####,#####,#####</pre>
 <h3 id="faq-dev-10">How do I create an options menu for my application?</h3>
 <p>
   You can let users set options for your extension by creating an
-  <a href="http://code.google.com/chrome/extensions/trunk/options.html">options page</a>,
+  <a href="/extensions/options.html">options page</a>,
   which is a simple HTML page that will be loaded when a user clicks the
   "options" button for your extension. This page can read and write settings
   to localStorage, or even send options to a web server so that they can be
@@ -327,7 +327,7 @@ cros,beta,#.#.###.#,#.#.###.#,mm/dd/yy,mm/dd/yy,#####,#####,#####</pre>
 <p>
   Chrome's built-in developer tools can be used to debug extensions
   as well as web pages. See this
-  <a href="http://code.google.com/chrome/extensions/tut_debugging.html ">tutorial on debugging extensions</a>
+  <a href="/extensions/tut_debugging.html ">tutorial on debugging extensions</a>
   for more information.
 </p>