Fix some typos, broken links and other issues in extension docs

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

 <h1>What's New in Extensions?</h1>
 <!--  -->
 
 <p>
 This page lists the API and manifest changes
 made in recent releases.
 </p>
 
 <h2 id="22"> Google Chrome 22 </h2>
 
@@ skipping 144 matching lines @@
 <h2 id="18"> Google Chrome 18 </h2>
 
 <h4> New APIs </h4>
   <ul>
     <li>The <a href="debugger.html">debugger API</a>
       lets you use the Chrome Developer Tools
       on one or more tabs remotely.
     <li>The <a href="devtools.html">developer tools APIs</a>
       provide support for extending Chrome Developer Tools.
       The inspected window API lets you interact with the inspected window.
-      The network API lets you retrive information about network requests.
+      The network API lets you retrieve information about network requests.
       The panels API lets you add panels and sidebars.
     <li>The <a href="pageCapture.html">page capture API</a>
       lets you save a tab as MHTML.
     <li> The <a href="privacy.html">privacy API</a>
       lets you control usage of the features
       in Chrome that can affect a user's privacy policy.
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
@@ skipping 13 matching lines @@
       <a href="background_pages.html">background.scripts</a> property
       and Chrome will generate a background page for you.
     <li>The new
       <a href="manifest.html#web_accessible_resources">web_accessible_resources</a>
       field specifies the paths of packaged resources
       that are expected to be usable in the context of a web page.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
-    <li>The $ref:windows.WINDOW_ID_CURRENT
+    <li>The $ref:[windows windows API]
     now has a <code>WINDOW_ID_CURRENT</code> property.

[not at google - send to devlin, 2013/02/11 14:06:46]

Could $ref:windows.WINDOW_ID_CURRENT directly but to be honest I don't think
this is actually worthy of being mentioned at all. Let's just delete it...

[方觉(Fang Jue), 2013/02/12 03:27:14]

Then delete it.

     <li>The <code>chrome.tabs</code>
     $ref:tabs.create and
     $ref:tabs.update methods
     now have an <code>openerTabId</code> parameter.
   </ul>
 
 <h2 id="17"> Google Chrome 17 </h2>
 
 <h4> New APIs </h4>
   <ul>
@@ skipping 83 matching lines @@
     To get details about all tabs in the specified window, use
     $ref:tabs.query
     with the argument <code>{'windowId': windowID}</code>.
     To get the tab that is selected in the specified window, use
     <code>chrome.tabs.query()</code>
     with the argument <code>{'active': true}</code>.
     <li>You are no longer required
     to specify the <code>tabID</code> for the
     $ref:tabs.update method.
     When not provided,
-    the <code>tabID</code> defaults
+    the <code>tabId</code> defaults
     to the selected tab of the current window.
     <li>External extension files on Mac OS can now be owned by users
     within a wheel group (or an admin group).
     <li>The "experimental" permission is no longer required
     for the
-    $ref:windows.Window type.
+    $ref:[windows.Window "panel"] type.
     By default, the "panel" type creates a popup
     unless the <code>--enable-panels</code> flag is set.
   </ul>
 
 <h2 id="15"> Google Chrome 15 </h2>
 
 <h4> New APIs </h4>
 
 <ul>
  <li>The <a href="webstore.html">webstore API</a>
@@ skipping 98 matching lines @@
   </ul>
 
 <h4> Manifest changes </h4>
   <ul>
     <li>A new <code>exclude_matches</code> item
       in the "content_scripts" field
       lets you target your content script more precisely.
       For details, see
       <a href="content_scripts.html#match-patterns-globs">Match patterns and globs</a>.
     <li>New "clipboardRead" and "clipboardWrite"
-      <a href="manifest.html#permissions">permissions</a>
+      <a href="declare_permissions.html">permissions</a>
       specify capabilities for <code>document.execCommand()</code>.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>Content scripts can now make
       <a href="xhr.html">cross-origin XMLHttpRequests</a>
       to the same sites that their parent extension can,
       eliminating the need to relay these requests
       through a background page.
@@ skipping 35 matching lines @@
   </ul>
 
 <h2 id="11"> Google Chrome 11 </h2>
 
 <h4> Changes to existing APIs </h4>
   <ul>
     <li>For security reasons, you can no longer call
       $ref:tabs.captureVisibleTab
       on just any tab.
       Instead, you now must have
-      <a href="manifest.html#permissions">host permission</a>
+      <a href="declare_permissions.html">host permission</a>
       for the URL displayed by that tab.
       To get the previous behavior,
       specify <code>&lt;all_urls></code> for the host permission.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>The management API's
       $ref:management.ExtensionInfo object
       now has a <code>homepageUrl</code> property.
     <li>The management API now lets you get the icons of
       disabled apps and extensions.
       Also, you can now modify the regular icon's URL
       to get its disabled equivalent.
       See $ref:management.IconInfo for details.
     <li>The cookies API
       $ref:cookies.set
       and $ref:cookies.remove methods
       can now take callbacks.
   </ul>
 
 <h2 id="10"> Google Chrome 10 </h2>
 
 <h4> Manifest changes </h4>
   <ul>
-    <li>The new <a href="manifest.html#bg">background</a> permission
+    <li>The new <a href="declare_permissions.html#bg">background</a> permission
       extends the life of Chrome,
       allowing your extension or app
       to run even when Chrome has no windows open.
   </ul>
 
 <h4> Additions to existing APIs </h4>
   <ul>
     <li>The $ref:windows.create
       method now has a <code>tabId</code> field.
       You can use it to move a tab or panel into a new window.
@@ skipping 93 matching lines @@
 <h4> Manifest changes </h4>
   <ul>
     <li>The <a href="manifest.html#geolocation">geolocation</a> permission
       gives an extension access to the user's physical location.
     <li><a href="match_patterns.html">Match patterns</a> can now select all
       schemes or all URLs.
     <li>Access to file:/// URLs no longer triggers the "access to your machine"
       security warning, but now requires user opt-in from the extensions
       management page.
   </ul>