NaCl docs: clarify Chrome apps instead of packaged apps

native_client_sdk/src/doc/devguide/tutorial/tutorial-part2.rst

 .. _tutorial2:
 
 ######################################
 C++ Tutorial: Getting Started (Part 2)
 ######################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 Overview
 ========
 
 This tutorial shows how to convert the finished PNaCl web application from
 :doc:`Part 1 <tutorial-part1>` to use the Native Client SDK build system and
 common JavaScript files. It also demonstrates some techniques to make your web
 application `Content Security Policy (CSP)-compliant
-</apps/contentSecurityPolicy>`_, which is necessary for `Chrome Apps
-</apps/about_apps>`_.
+</apps/contentSecurityPolicy>`_, which is necessary for `Chrome Apps </apps>`_.
 
 Using the Native Client SDK build system makes it easy to build with all of the
 SDK toolchains, and switch between the Debug and Release configurations. It
 also simplifies the makefiles for your project, as we'll see in the next
 section. Finally, it adds some useful commands for :ref:`running
 <running_the_sdk_examples>` and :ref:`debugging <debugging_the_sdk_examples>`
 your application.
 
 The finished code for this example can be found in the
 ``pepper_$(VERSION)/getting_started/part2`` directory in the Native Client SDK
@@ skipping 194 matching lines @@
 
 .. naclcode::
 
     $(eval $(call NMF_RULE,$(TARGET),))
 
 Making index.html work for Chrome Apps
 ======================================
 
 This section describes the changes necessary to make the HTML and JavaScript in
 part1 CSP-compliant. This is required if you want to build a `Chrome App
-</apps/about_apps>`_, but is not necessary if you want to use PNaCl on the open
-web.
+</apps>`_, but is not necessary if you want to use PNaCl on the open web.
 
 CSP rules
 ---------
 
 `Chrome Apps CSP </apps/contentSecurityPolicy#what>`_ restricts you from doing
 the following:
 
 * You can’t use inline scripting in your Chrome App pages. The restriction
   bans both ``<script>`` blocks and event handlers (``<button onclick="...">``).
 * You can’t reference any external resources in any of your app files (except
@@ skipping 255 matching lines @@
 Compile the Native Client module and run the application again
 ==============================================================
 
 #. Compile the Native Client module by running the ``make`` command again.
 #. Start the SDK web server by running ``make server``.
 #. Re-run the application by reloading ``http://localhost:5103/part2`` in 
    Chrome.
    
    After Chrome loads the Native Client module, you should see the message sent
    from the module.