Remove .html extension from links

chrome/common/extensions/docs/templates/intros/webNavigation.html

 <h2 id="manifest">Manifest</h2>
 <p>
 All <code>chrome.webNavigation</code> methods and events require you to declare
-the "webNavigation" permission in the <a href="manifest.html">extension
+the "webNavigation" permission in the <a href="manifest">extension
 manifest</a>.
 For example:
 </p>
 
 <pre data-filename="manifest.json">
 {
   "name": "My extension",
   ...
   <b>"permissions": [
     "webNavigation"
   ]</b>,
   ...
 }
 </pre>
 
 
 <h2 id="examples">Examples</h2>
 
 <p>
 You can find simple examples of using the tabs module in the
 <a href="http://src.chromium.org/viewvc/chrome/trunk/src/chrome/common/extensions/docs/examples/api/webNavigation/">examples/api/webNavigation</a>
 directory.
 For other examples and for help in viewing the source code, see
-<a href="samples.html">Samples</a>.
+<a href="samples">Samples</a>.
 </p>
 
 <h2 id="event_order">Event order</h2>
 <p>
 For a navigation that is successfully completed, events are fired in the
 following order:
 <pre>
 onBeforeNavigate -&gt; onCommitted -&gt; onDOMContentLoaded -&gt; onCompleted
 </pre>
 </p>
@@ skipping 24 matching lines @@
 href="https://support.google.com/chrome/bin/answer.py?answer=177873">Chrome
 Instant</a> or <a
 href="https://support.google.com/chrome/bin/answer.py?answer=1385029">Instant
 Pages</a>, a completely loaded page is swapped into the current tab. In that
 case, an <code>onTabReplaced</code> event is fired.
 </p>
 
 <h2 id="relation_to_webRequest">Relation to webRequest events</h2>
 <p>
 There is no defined ordering between events of the <a
-href="webRequest.html">webRequest API</a> and the events of the
+href="webRequest">webRequest API</a> and the events of the
 webNavigation API. It is possible that webRequest events are still received for
 frames that already started a new navigation, or that a navigation only
 proceeds after the network resources are already fully loaded.
 </p>
 <p>
 In general, the webNavigation events are closely related to the navigation
 state that is displayed in the UI, while the webRequest events correspond to
 the state of the network stack which is generally opaque to the user.
 </p>
 
 <h2 id="tab_ids">A note about tab IDs</h2>
 <p>
 Not all navigating tabs correspond to actual tabs in Chrome's UI, e.g., a tab
 that is being pre-rendered. Such tabs are not accessible via the
-<a href="tabs.html">tabs API</a> nor can you request information about them via
+<a href="tabs">tabs API</a> nor can you request information about them via
 <code>webNavigation.getFrame</code> or <code>webNavigation.getAllFrames</code>.
 Once such a tab is swapped in, an <code>onTabReplaced</code> event is fired and
 they become accessible via these APIs.
 </p>
 
 <h2 id="timestamps">A note about timestamps</h2>
 <p>
 It's important to note that some technical oddities in the OS's handling
 of distinct Chrome processes can cause the clock to be skewed between the
 browser itself and extension processes. That means that WebNavigation's events'
@@ skipping 20 matching lines @@
 case, you will receive repeated <code>onBeforeNavigate</code> and
 <code>onErrorOccurred</code> events, until you receive the final
 <code>onCommitted</code> event.
 </p>
 
 <h2 id="transition_types">Transition types and qualifiers</h2>
 <p>
 The webNavigation API's <code>onCommitted</code> event has a
 <code>transitionType</code> and a <code>transitionQualifiers</code> property.
 The <em>transition type</em> is the same as used in the <a
-href="history.html#transition_types">history API</a> describing how the browser
+href="history#transition_types">history API</a> describing how the browser
 navigated to this particular URL. In addition, several <em>transition
 qualifiers</em> can be returned that further define the navigation.
 </p>
 <p>
 The following transition qualifiers exist:
 </p>
 <table>
 <tr>
   <th> Transition qualifier </th> <th> Description </th>
 </tr>
@@ skipping 17 matching lines @@
     The user used the Forward or Back button to initiate the navigation.
   </td>
 </tr>
 <tr>
   <td>"from_address_bar"</td>
   <td>
     The user initiated the navigation from the address bar (aka Omnibox).
   </td>
 </tr>
 </table>