Index: chrome/common/extensions/docs/templates/articles/manifest/sandbox.html |
diff --git a/chrome/common/extensions/docs/templates/articles/manifest/sandbox.html b/chrome/common/extensions/docs/templates/articles/manifest/sandbox.html |
index 495061d1155a3577096c9da939e2de2262ddd716..39ac817ffd5e8c277f2d4fa9cbdf8ba5c81bb7a5 100644 |
--- a/chrome/common/extensions/docs/templates/articles/manifest/sandbox.html |
+++ b/chrome/common/extensions/docs/templates/articles/manifest/sandbox.html |
@@ -12,7 +12,7 @@ direct access to non-sandboxed pages (it may communicate with them via |
<code>postMessage()</code>).</li> |
<li> |
<p>A sandboxed page is not subject to the |
- <a href="http://developer.chrome.com/extensions/contentSecurityPolicy.html">Content Security Policy |
+ <a href="http://developer.chrome.com/extensions/contentSecurityPolicy">Content Security Policy |
(CSP)</a> used by the rest of the app or extension (it has its own separate |
CSP value). This means that, for example, it can use inline script and |
<code>eval</code>.</p> |
@@ -56,14 +56,14 @@ that embeds them. |
</p> |
<p> |
-<a href="http://developer.chrome.com/extensions/sandboxingEval.html">"Using eval in Chrome Extensions. Safely."</a> |
+<a href="http://developer.chrome.com/extensions/sandboxingEval">"Using eval in Chrome Extensions. Safely."</a> |
goes into more detail about implementing a sandboxing workflow that enables use |
of libraries that would otherwise have issues executing under extension's |
-<a href="http://developer.chrome.com/extensions/contentSecurityPolicy.html">default Content Security |
+<a href="http://developer.chrome.com/extensions/contentSecurityPolicy">default Content Security |
Policy</a>. |
</p> |
<p> |
Sandboxed page may only be specified when using |
-<a href="http://developer.chrome.com/extensions/manifest.html#manifest_version"><code>manifest_version</code></a> 2 or above. |
+<a href="http://developer.chrome.com/extensions/manifest#manifest_version"><code>manifest_version</code></a> 2 or above. |
</p> |