Remove "View Background Pages".

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

 <h1>Event Pages</h1>
 
 
 <p>
 Event pages are very similar to
 <a href="background_pages.html">background pages</a>,
 with one important difference:
 event pages are loaded only when they are needed.
 When the event page is not actively doing something,
 it is unloaded, freeing memory and other system resources.
@@ skipping 72 matching lines @@
 API or issuing a network request). Additionally, the
 event page will not unload until all visible views (for example,
 popup windows) are closed and all message ports are closed. Note
 that opening a view does not cause the event page to load, but
 only prevents it from closing once loaded.
 </p>
 
 <p>
 Make sure your event page closes as soon as the event that
 opened it is processed.
-You can observe the lifetime of your event page by clicking
-on "View Background Pages" in the Chrome menu, or by
+You can observe the lifetime of your event page by
 opening Chrome's task manager. You can see when your event
 page loads and unloads by observing when an entry for your
 extension appears in the list of processes.
 </p>
 
 <p>
 Once the event page has been idle a short time
 (a few seconds), the
 <code>$ref:runtime.onSuspend</code>
 event is dispatched. The event page has a few more seconds to handle this
@@ skipping 107 matching lines @@
   <code>$ref:contextMenus.create</code>.
 
   <li>Remember to test that your event page works properly when it is unloaded
   and then reloaded, which only happens after several seconds of inactivity. 
   Common mistakes include doing unnecessary work at page load time (when it
   should only be done when the extension is installed); setting an alarm at
   page load time (which resets any previous alarm); or not adding event
   listeners at page load time.
 </ol>
 </p>