Remove .html extension from links

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

 <h1>Permission Warnings</h1>
 
 
 <!--
 NOTE: When this doc is updated, the online help should also be updated:
 http://www.google.com/support/chrome_webstore/bin/answer.py?hl=en&answer=186213
 
 We should periodically look at
 http://src.chromium.org/viewvc/chrome/trunk/src/chrome/app/generated_resources.grd?view=markup
 to make sure that we're covering all messages. Search for
 IDS_EXTENSION_PROMPT_WARNING
 (e.g. IDS_EXTENSION_PROMPT_WARNING_BROWSING_HISTORY).
 -->
 
 <p>
 To use most chrome.* APIs and extension capabilities,
 your extension must declare its intent in the
-<a href="manifest.html">manifest</a>,
+<a href="manifest">manifest</a>,
 often in the "permissions" field.
 Some of these declarations
 result in a warning when
 a user installs your extension.
 </p>
 
 <p>
 When you autoupdate your extension,
 the user might see another warning
 if the extension requests new permissions.
@@ skipping 114 matching lines @@
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_FULL_ACCESS -->
     Access all data on your computer and the websites you visit
   </td>
   <td>
     "plugins"
   </td>
   <td>
     The "plugins" permission is required by
-    <a href="npapi.html">NPAPI plugins</a>.
+    <a href="npapi">NPAPI plugins</a>.
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_BOOKMARKS -->
     Read and modify your bookmarks
   </td>
   <td>
     "bookmarks" permission
   </td>
   <td>
     The "bookmarks" permission is required by the
-    <a href="bookmarks.html"><code>chrome.bookmarks</code></a> module.
+    <a href="bookmarks"><code>chrome.bookmarks</code></a> module.
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_BROWSING_HISTORY -->
     Read and modify your browsing history
   </td>
   <td>
     <!-- HasEffectiveBrowsingHistoryPermission -->
      Any of the following:
     <ul>
       <li> "history" permission </li>
       <li> "topSites" permission </li>
     </ul>
   </td>
   <td>
     <p>
       The "history" permission is required by
-      <a href="history.html"><code>chrome.history</code></a>.
+      <a href="history"><code>chrome.history</code></a>.
     </p>
     <p>
       The "topSites" permission is required by
-      <a href="topSites.html"><code>chrome.topSites</code></a>.
+      <a href="topSites"><code>chrome.topSites</code></a>.
     </p>
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_TABS -->
     Access your tabs and browsing activity
   </td>
   <td>
     <!-- HasEffectiveBrowsingHistoryPermission -->
     Any of the following:
     <ul>
       <li> "tabs" permission </li>
       <li> "webNavigation" permission </li>
     </ul>
   </td>
   <td>
     <p>
       The "tabs" permission is required by the
-      <a href="tabs.html"><code>chrome.tabs</code></a> and
-      <a href="windows.html"><code>chrome.windows</code></a> modules.
+      <a href="tabs"><code>chrome.tabs</code></a> and
+      <a href="windows"><code>chrome.windows</code></a> modules.
     </p>
     <p>
       The "webNavigation" permission is required by the
-      <a href="webNavigation.html"><code>chrome.webNavigation</code></a> module.
+      <a href="webNavigation"><code>chrome.webNavigation</code></a> module.
     </p>
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_CONTENT_SETTINGS -->
     Manipulate settings that specify whether websites can use features such as cookies, JavaScript, and plug-ins
   </td>
   <td>
     <!-- HasEffectiveBrowsingHistoryPermission -->
      "contentSettings" permission
   </td>
   <td>
     <p>
       The "contentSettings" permission is required by
-      <a href="contentSettings.html"><code>chrome.contentSettings</code></a>.
+      <a href="contentSettings"><code>chrome.contentSettings</code></a>.
     </p>
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_ALL_HOSTS -->
     Access your data on all websites
   </td>
   <td>
     <!-- HasEffectiveAccessToAllHosts() -->
     Any of the following:
     <ul>
       <li> "debugger" permission </li>
       <li> "pageCapture" permission </li>
       <li> "proxy" permission </li>
       <li> A match pattern in the "permissions" field
         that matches all hosts </li>
       <li> A&nbsp;"content_scripts" field with a "matches" entry
         that matches all hosts </li>
       <li> "devtools_page" </li>
     </ul>
   </td>
   <td>
     <p>
       The "debugger" permission is required by the
-      <a href="debugger.html">debugger</a> module.
+      <a href="debugger">debugger</a> module.
     </p>
 
     <p>
       The "proxy" permission is required by the
-      <a href="proxy.html"><code>chrome.proxy</code></a> module.
+      <a href="proxy"><code>chrome.proxy</code></a> module.
     </p>
 
     <p>
       Any of the following URLs match all hosts:
     </p>
     <ul>
       <li> <code>http://*/*</code> </li>
       <li> <code>https://*/*</code> </li>
       <li> <code>*://*/*</code> </li>
       <li> <code>&lt;all_urls&gt;</code> </li>
     </ul>
-    <strong>Note that you may be able to avoid declaring all host permissions using the <code><a href="activeTab.html">activeTab</a></code> permission.</strong>
+    <strong>Note that you may be able to avoid declaring all host permissions using the <code><a href="activeTab">activeTab</a></code> permission.</strong>
   </td>
 </tr>
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_?_HOST -->
     <!-- IDS_EXTENSION_PROMPT_WARNING_4_OR_MORE_HOSTS -->
     Access your data on <em>{list of websites}</em>
   </td>
   <td>
     A match pattern in the "permissions" field
@@ skipping 26 matching lines @@
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_MANAGEMENT -->
     Manage your apps, extensions, and themes
   </td>
   <td>
     "management" permission
   </td>
   <td>
     The "management" permission is required by the
-    <a href="management.html"><code>chrome.management</code></a> module.
+    <a href="management"><code>chrome.management</code></a> module.
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_GEOLOCATION -->
     Detect your physical location
   </td>
   <td>
     "geolocation" permission
@@ skipping 26 matching lines @@
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_PRIVACY-->
     Manipulate privacy-related settings
   </td>
   <td>
     "privacy" permission
   </td>
   <td>
     The "privacy" permission is required by the
-    <a href="privacy.html"><code>chrome.privacy</code></a> module.
+    <a href="privacy"><code>chrome.privacy</code></a> module.
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_SIGNED_IN_DEVICES-->
     Access the list of your signed-in devices
   </td>
   <td>
     "signedInDevices" permission
   </td>
   <td>
     The "signedInDevices" permission is required by the
-    <a href="signedInDevices.html"><code>chrome.signedInDevices</code></a>
+    <a href="signedInDevices"><code>chrome.signedInDevices</code></a>
     module.
   </td>
 </tr>
 
 <tr>
   <td style="font-weight:bold">
     <!-- IDS_EXTENSION_PROMPT_WARNING_TTS_ENGINE-->
     Access all text spoken using synthesized speech
   </td>
   <td>
     "ttsEngine" permission
   </td>
   <td>
     The "ttsEngine" permission is required by the
-    <a href="ttsEngine.html"><code>chrome.ttsEngine</code></a> module.
+    <a href="ttsEngine"><code>chrome.ttsEngine</code></a> module.
   </td>
 </tr>
 </table>
 </p>
 
 
 <h2 id="nowarning"> Permissions that don't cause warnings </h2>
 
 <p>
 The following permissions don't result in a warning:
@@ skipping 21 matching lines @@
   <li>"storage"</li>
   <li>"unlimitedStorage"</li>
   <li>"webRequest"</li>
   <li>"webRequestBlocking"</li>
 </ul>
 
 <h2 id="test"> Testing permission warnings </h2>
 
 <p>
 If you'd like to see exactly which warnings your users will get,
-<a href="packaging.html">package your extension</a>
+<a href="packaging">package your extension</a>
 into a <code>.crx</code> file,
 and install it.
 </p>
 
 <p>
 To see the warnings users will get when your extension is autoupdated,
 you can go to a little more trouble
 and set up an autoupdate server.
 To do this, first create an update manifest
 and point to it from your extension,
 using the "update_url" key
-(see <a href="autoupdate.html">Autoupdating</a>).
-Next, <a href="packaging.html">package the extension</a>
+(see <a href="autoupdate">Autoupdating</a>).
+Next, <a href="packaging">package the extension</a>
 into a new <code>.crx</code> file,
 and install the app from this <code>.crx</code> file.
 Now, change the extension's manifest to contain the new permissions,
-and <a href="packaging.html#update">repackage the extension</a>.
+and <a href="packaging#update">repackage the extension</a>.
 Finally, update the extension
 (and all other extensions that have outstanding updates)
 by clicking the <b>chrome://extensions</b> page's
 <b>Update extensions now</b> button.
 </p>
 
 <h2 id="api">API</h2>
 
 <p>
 You can get a list of permission warnings for any manifest with
 $(ref:management.getPermissionWarningsByManifest).
 </p>