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

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

 <h1>Frequently Asked Questions</h1>
 
 
 <!--  -->
 
 <p>
 If you don't find an answer to your question here,
 try the
 <a href="http://code.google.com/chrome/webstore/faq.html">Chrome Web Store FAQ</a>, the
 <a href="http://stackoverflow.com/questions/tagged/google-chrome-extension">[google-chrome-extension] tag on Stack Overflow</a>, the
@@ skipping 71 matching lines @@
   <p>
   Click the Chrome menu icon
   <img src="{{static}}/images/hotdogmenu.png" height="29" width="29" alt=""
     class="nomargin" />
   and select <b>Extensions</b> from the <b>Tools</b> menu.
   Ensure that the "Developer mode" checkbox in the top right-hand corner
   is checked.
   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}}
 
 <h3 id="faq-gen-02">What technologies are used to write extensions for Chrome?</h3>
 <p>
   Extensions are written using the same standard web
   technologies that developers use to create websites. HTML is used as a
   content markup language, CSS is used for styling, and JavaScript for
   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>
 
 
 <h3 id="faq-gen-03">Are extensions fetched from the web every time the browser is loaded?</h3>
 <p>
   Extensions are downloaded by the Chrome browser upon install, and
   are subsequently run off of the local disk in order to speed up
   performance. However, if a new version of the extension is pushed online,
@@ skipping 40 matching lines @@
   combination.  The rest of the information is metadata about when the releases
   were first pushed, as well as revision numbers associated with each build.
 </p>
 
 
 <h2 id="capabilities2">Capabilities</h2>
 
 <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>
 
 <h3 id="faq-dev-03">Can extensions use 3rd party web services?</h3>
 <p>
   Yes. Extensions are capable of making cross-domain Ajax
   requests, so they can call remote APIs directly. APIs that provide data
   in JSON format are particularly easy to use.
 </p>
 
@@ skipping 132 matching lines @@
 
 <h3 id="faq-dev-09">How much data can I store in localStorage?</h3>
 <p>
   Extensions can store up to 5MB of data in localStorage.
 </p>
 
 {{^is_apps}}
 <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
   persisted across browsers.
 </p>
 {{/is_apps}}
 
 <h3 id="faq-dev-12">What debugging tools are available to extension developers?</h3>
 <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>
 
 <h3 id="faq-dev-16">Why do wildcard matches not work for top level domains
   (TLDs)?</h3>
 <p>
   You cannot use wildcard match patterns like <code>http://google.*/*</code>
   to match TLDs (like <code>http://google.es</code> and
   <code>http://google.fr</code>) due to the
   complexity of actually restricting such a match to only the desired domains.
@@ skipping 141 matching lines @@
     <a href="http://groups.google.com/a/chromium.org/group/chromium-extensions/topics">
     discussion group</a> with a link back to your request.
   </li>
   <li>
     If you originally reported your request on the discussion group and were
     directed to this FAQ entry, reply to your original thread with a link
     to the ticket you starred or opened.  This will make it easier for others
     with the same request to find the correct ticket.
   </li>
 </ol>