Doc server manifest page generation

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

 <h1>Background Pages</h1>
 
 
 <p id="eventPageWarning" class="warning">
   <em>Caution:</em> Consider using event pages instead.
   <a href="event_pages.html">Learn more</a>.
 </p>
 
 <p>
 A common need for extensions is to have
 a single long-running script to manage some task or state.
 Background pages to the rescue.
 </p>
 
 <p>
 As the <a href="overview.html#arch">architecture overview</a> explains,
 the background page is an HTML page that runs in the extension process.
 It exists for the lifetime of your extension,
 and only one instance of it at a time is active. (Exception: if your
-extension uses <a href="manifest.html#incognito">incognito</a>
+extension uses <a href="manifest/incognito.html">incognito</a>
 "split" mode, a second instance is created for incognito windows.)
 </p>
 
 <p>
 In a typical extension with a background page,
 the UI &mdash;
 for example, the browser action or page action
 and any options page &mdash;
 is implemented by dumb views.
 When the view needs some state,
@@ skipping 122 matching lines @@
   &lt;body>
     &lt;p>
     Image here:
     &lt;/p>
 
     &lt;img id="target" src="white.png" width="640" height="480">
 
   &lt;/body>
 &lt;/html>
 </pre>