[NaCl SDK Docs] Simplify PPAPI documentation generation.

native_client_sdk/src/doc/faq.rst

 ##########################
 Frequently Asked Questions
 ##########################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 This document answers some frequently asked questions about Native
@@ skipping 234 matching lines @@
 we consider requirements for a production-quality system that keeps the
 user safe are difficult to implement without help from the
 browser. Specific examples are an out-of-process plugin architecture and
 appropriate interfaces for integrated 3D graphics. We have worked
 closely with Chromium developers to deliver these features and we are
 eager to collaborate with developers from other browsers.
 
 What's the difference between NPAPI and Pepper?
 -----------------------------------------------
 
-:doc:`Pepper <peppercpp/index>` (also known as PPAPI) is a new API that
+:doc:`Pepper <pepper_stable/index>` (also known as PPAPI) is a new API that
 lets Native Client modules communicate with the browser. Pepper supports
 various features that don't have robust support in NPAPI, such as event
 handling, out-of-process plugins, and asynchronous interfaces. Native
 Client has transitioned from using NPAPI to using Pepper.
 
 Is NPAPI part of the Native Client SDK?
 ---------------------------------------
 
 NPAPI is not supported by the Native Client SDK, and is `deprecated in
 Chrome
@@ skipping 296 matching lines @@
   you're loading the correct ``.nexe`` file by building a separate
   ``.nexe`` for each architecture, and using a ``.nmf`` manifest file to
   let the browser select the correct ``.nexe`` file. Note: the need to
   select a processor-specific ``.nexe`` goes away with Portable Native
   Client.
 * If things still aren't working, :doc:`ask for help <help>`!
 
 .. _CORS: http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
 .. _naclports: https://code.google.com/p/naclports
 .. _Crouton: https://github.com/dnschneid/crouton