Doc server manifest page generation

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

 <h1>Embed Content</h1>
 
 
 <p>
 The <a href="app_architecture.html#security">packaged apps security model</a> disallows
 external content in iframes and
 the use of inline scripting and <code>eval()</code>.
 You can override these restrictions,
 but your external content must be isolated from the app.
 </p>
@@ skipping 107 matching lines @@
 
 <h2 id="sandboxing">Sandbox local content</h2>
 
 <p>
 Sandboxing allows specified pages
 to be served in a sandboxed, unique origin.
 These pages are then exempt from their Content Security Policy.
 Sandboxed pages can use iframes, inline scripting,
 and <code>eval()</code>.
 Check out the manifest field description for
-<a href="manifest.html#sandbox">sandbox</a>.
+<a href="manifest/sandbox.html">sandbox</a>.
 </p>
 
 <p>
 It's a trade-off though:
 sandboxed pages can't use the chrome.* APIs.
 If you need to do things like <code>eval()</code>,
 go this route to be exempt from CSP,
 but you won't be able to use the cool new stuff.
 </p>
 
@@ skipping 139 matching lines @@
 
 <pre>
 var messageHandler = function(e) {
   console.log('Background script says hello.', e.data);
 };
 
 window.addEventListener('message', messageHandler);
 </pre>
 
 <p class="backtotop"><a href="#top">Back to top</a></p>