PNaClize and update the 'Devguide -> Running' page of the documentation.

native_client_sdk/src/doc/sdk/examples.rst

 .. _sdk-examples-2:
 
 Running the SDK Examples
 ========================
 
 Every Native Client SDK bundle comes with a folder of example applications.
 Each example demonstrates one or two key Native Client programming concepts.
 After you've :doc:`downloaded the SDK <download>`, follow the instructions
 on this page to build and run the examples.
 
@@ skipping 141 matching lines @@
 .nexe files, for ease of debugging. All Debug and Release directories contain
 a manifest (.nmf) file that references the associated .nexe or .pexe files.
 For information about Native Client manifest files, see the :doc:`Technical
 Overview <../overview>`.
 
 For details on how to use ``make``, see the `GNU 'make' Manual
 <http://www.gnu.org/software/make/manual/make.html>`_. For details on how to
 use the SDK toolchain itself, see :doc:`Building Native Client Modules
 <../devguide/devcycle/building>`.
 
+.. _run_sdk_examples:
+
 Run the SDK examples
 --------------------
 
 To run the SDK examples, you can use the ``make run`` command::
 
   $ cd pepper_31/examples/api/core
   $ make run
 
 This will launch a local HTTP server which will serve the data for the
 example. It then launches Chrome with the address of this server, usually
@@ skipping 23 matching lines @@
   $ export CHROME_PATH=<Path to chrome>
 
 .. **TODO(binji):** use default Chrome paths here, especially
 .. important for Mac:
 
 You can run via a different toolchain or configuration by using the
 ``TOOLCHAIN`` and ``CONFIG`` parameters to make::
 
   $ make run TOOLCHAIN=pnacl CONFIG=Debug
 
+.. _run_sdk_examples_as_packaged:
 
 Run the SDK examples as packaged apps
 -------------------------------------
 
 Each example can also be launched as a packaged app. For more information about
 using Native Client for packaged apps, see :ref:`Packaged appliction
 <distributing_packaged>`.  For general information about packaged apps, see the
 `Chrome apps documentation
 <http://developer.chrome.com/apps/about_apps.html>`_.
 
@@ skipping 34 matching lines @@
 
 At this point, you can use the standard GDB commands to debug your NaCl module.
 The most common commands you will use to debug are ``continue``, ``step``,
 ``next``, ``break`` and ``backtrace``. See :doc:`Debugging
 <../devguide/devcycle/debugging>` for more information about debugging a Native Client
 application.
 
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. |gear-icon| image:: /images/gear-icon.png