Remove .html extension from links

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

 <h1>Content Security Policy</h1>
 
 
 <p>
 If you're not familiar with Content Security Policy (CSP),
 <a href="http://www.html5rocks.com/en/tutorials/security/content-security-policy/">An Introduction to Content Security Policy</a>
 is a good starting point.
 That document covers the broader web platform view of CSP;
 Chrome App CSP isn't as flexible.
 You should also read the
-<a href="/extensions/contentSecurityPolicy.html">Chrome extension Content Security Policy</a>,
+<a href="/extensions/contentSecurityPolicy">Chrome extension Content Security Policy</a>,
 as it's the foundation for the Chrome App CSP.
 For brevity's sake,
 we don't repeat the same information here.
 </p>
 
 <p>
 CSP is a policy to mitigate against cross-site scripting issues,
 and we all know that cross-site scripting is bad.
 We aren’t going to try and convince you
 that CSP is a warm-and-fuzzy new policy.
@@ skipping 69 matching lines @@
 You can still use a library that doesn’t offer precompilation,
 but it will require some work on your part and there are restrictions.
 </p>
 
 <p>
 You will need to use sandboxing to isolate any content
 that you want to do ‘eval’ things to.
 Sandboxing lifts CSP on the content that you specify.
 If you want to use the very powerful Chrome APIs in your Chrome App,
 your sandboxed content can't directly interact with these APIs
-(see <a href="app_external.html#sandboxing">Sandbox local content</a>).
+(see <a href="app_external#sandboxing">Sandbox local content</a>).
 </p>
 
 <h3 id="remote_resources">Access remote resources</h3>
 
 <p>
 You can fetch remote resources via <code>XMLHttpRequest</code>
 and serve them via <code>blob:</code>, <code>data:</code>,
 or <code>filesystem:</code> URLs
-(see <a href="app_external.html#external">Referencing external resources</a>).
+(see <a href="app_external#external">Referencing external resources</a>).
 </p>
 
 <p>
 Video and audio can be loaded from remote services
 because they have good fallback behavior when offline or under spotty connectivity.
 </p>
 
 <h3 id="embed_content">Embed web content</h3>
 
 <p>
 Instead of using an iframe,
 you can call out to an external URL using an object tag
-(see <a href="app_external.html#webview">Embed external web pages</a>).
+(see <a href="app_external#webview">Embed external web pages</a>).
 </p>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>