Doc server manifest page generation

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

 <h1>Manifest Version</h1>
 
 <style type="text/css">
 #schedule h3 {
   margin-bottom:0;
 }
 
 #schedule p {
   margin-top:0;
   margin-bottom:1em;
@@ skipping 85 matching lines @@
       <a href="../extensions/contentSecurityPolicy.html">
       <code>content_security_policy</code></a> documentation.
     </p>
   </li>
   <li>
     <p>
       A package's resources are no longer available by default to external
       websites (as the <code>src</code> of an image, or a <code>script</code>
       tag). If you want a website to be able to load a resource contained in
       your package, you'll need to explicitly whitelist it via the
-      <a href="manifest.html#web_accessible_resources">
+      <a href="manifest/web_accessible_resources.html">
         <code>web_accessible_resources</code>
       </a> manifest attribute. This is particularly relevant for extensions that
       build up an interface on a website via injected content scripts.
     </p>
   </li>
   <li>
     <p>
       The <code>background_page</code> property has been replaced with a
       <code>background</code> property that contains <em>either</em> a
       <code>scripts</code> or <code>page</code> property. Details are available
@@ skipping 102 matching lines @@
     </p>
   </li>
   <li>
     <p>
       <code>Port.tab</code> is gone. Use
       $ref:runtime.Port
       instead.
     </p>
   </li>
 </ul>