Remove .html extension from links

chrome/common/extensions/docs/templates/articles/manifest/nacl_modules.html

 <h1 id="nacl_modules">Manifest - Nacl Modules</h1>
 
 <p>
 One or more mappings from MIME types to the Native Client module
 that handles each type.
 For example, the bold code in the following snippet
 registers a Native Client module as the content handler
 for the OpenOffice spreadsheet MIME type.
 </p>
 
 <pre data-filename="manifest.json">
 {
   "name": "Native Client OpenOffice Spreadsheet Viewer",
   "version": "0.1",
   "description": "Open OpenOffice spreadsheets, right in your browser.",
   <b>"nacl_modules": [{
     "path": "OpenOfficeViewer.nmf",
     "mime_type": "application/vnd.oasis.opendocument.spreadsheet"
   }]</b>
 }
 </pre>
 
 <p>
 The value of "path" is the location of a Native Client manifest
 (a <code>.nmf</code> file)
 within the extension directory.
 For more information on Native Client and <code>.nmf</code> files, see the
-<a href="http://code.google.com/chrome/nativeclient/docs/technical_overview.html">Native Client Technical Overview</a>.
+<a href="http://code.google.com/chrome/nativeclient/docs/technical_overview">Native Client Technical Overview</a>.
 </p>
 
 <p>
 Each MIME type can be associated with only one <code>.nmf</code> file,
 but a single <code>.nmf</code> file might handle multiple MIME types.
 The following example shows an extension
 with two <code>.nmf</code> files
 that handle three MIME types.
 </p>
 
@@ skipping 18 matching lines @@
 </pre>
 
 <p class="note">
 <strong>Note:</strong>
 You can use Native Client modules in extensions
 without specifying "nacl_modules".
 Use "nacl_modules" only if you want the browser
 to use your Native Client module
 to display a particular type of content.
 </p>