Remove .html extension from links

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

 <h1>Packaging</h1>
 
 
 <p>
 This page describes how to package your extension.
-As the <a href="overview.html">Overview</a> explains,
+As the <a href="overview">Overview</a> explains,
 extensions are packaged as signed ZIP files
 with the file extension "crx"&mdash;for example,
 <code>myextension.crx</code>.
 </p>
 
 <p>
 <b>Note:</b>
 You do not need to package your own extension.
 If you publish your extension using the
 <a href="https://chrome.google.com/webstore/developer/dashboard">Chrome Developer Dashboard</a>,
 then the only reason to create your own <code>.crx</code> file
 would be to distribute a non-public version&mdash;for example,
 to alpha testers.
 You can find information on publishing extensions and apps in the
 Chrome Web Store getting started tutorial, starting at
-<a href="http://code.google.com/chrome/webstore/docs/get_started_simple.html#step5">Step 5: Zip up your app</a>.
+<a href="http://code.google.com/chrome/webstore/docs/get_started_simple#step5">Step 5: Zip up your app</a>.
 </p>
 
 <p>
 When you package an extension,
 the extension is assigned a unique key pair.
 The extension's ID is based on a hash of the public key.
 The private key is used to sign each version of the extension
 and must be secured from public access.
 Be careful not to include your private key within
 your extensions!
@@ skipping 146 matching lines @@
 For example:
 </p>
 
 <pre>
 chrome.exe --pack-extension=C:\myext --pack-extension-key=C:\myext.pem
 </pre>
 
 <h2 id="format">Package format and scripts</h2>
 <p>
 For more information on the format, as well as pointers to scripts you can use
-to create <code>.crx</code> files, see <a href="crx.html">CRX Package Format</a>.
+to create <code>.crx</code> files, see <a href="crx">CRX Package Format</a>.
 </p>