Doc server manifest page generation

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

 <meta name="doc-family" content="apps">
 <h1>Google Cloud Messaging for Chrome</h1>
 
 <p>
 Google Cloud Messaging for Chrome (GCM) is a service
 for signed-in Chrome users
 that helps developers send message data from servers
 to their Chrome apps and extensions.
 The service is intended to wake up an app or extension,
 and/or alert a user.
@@ skipping 467 matching lines @@
 from sending messages to your app or extension without your permission.
 If your app or extension attempts to use the pushMessaging API and
 the ownership check fails, it will receive
 HTTP status code 500 (Internal Server Error).
 </p>
 
 <p>
 One circumstance in which the ownership check commonly fails is when you are
 developing an app and you run the app without uploading it and re-downloading
 it from the Chrome Web Store. In this situation your app may not have a
-<a href="manifest.html#key">key</a> field in its manifest.json file.
+<a href="manifest/key.html">key</a> field in its manifest.json file.
 The <code>key</code> field gives an app its Chrome Web Store ID
 (a 32 character alphabetic code, such as "bafimiidcfafikaonocgmmcpbbhfjjik").
 If you run a version of your app without a key, the app will use a
 randomly generated ID that will not match the app's ID in the Chrome Web Store.
 For example, if you upload your app to the Chrome Web Store from the directory
 original_app_dir, then download the app and unpack it to downloaded_app_dir,
 and then run the exact same app as an unpacked extension from original_app_dir,
 the manifest.json file of the app in original_app_dir would not have
 the downloaded key, and the app's ID would appear to be different than
 the ID of the downloaded app.
@@ skipping 37 matching lines @@
   Extensions management page (chrome://extensions).</li>
 </ol>
 
 <p>
 Each time you reload your app or extension for testing,
 you need to check that the key is present in the manifest file.
 And anytime you wish to update the published version in the Chrome Web Store,
 you need to remove the key because the Store does not currently allow manifests
 with keys.
 </p>