NaCl docs: clarify Chrome apps instead of packaged apps

native_client_sdk/src/doc/devguide/devcycle/running.rst

 .. _devcycle-running:
 
 #######
 Running
 #######
 
 
 .. contents::
   :local:
   :backlinks: none
@@ skipping 27 matching lines @@
 ===================================================
 
 Before reading about how to run Native Client applications, it's important to
 understand a little bit about how Native Client applications are distributed.
 As explained in :doc:`Distributing Your Application <../distributing>`, Native
 Client applications must currently be distributed through the **Chrome Web
 Store (CWS)**. Applications in the CWS are one of three types:
 
 * A **hosted application** is an application that you host on a server of your
   choice. To distribute an application as a hosted application, you upload
-  application metadata to the CWS.
+  application metadata to the CWS. Learn more on the `Chrome App </apps>`_
+  documentation page.
 
 * A **packaged application** is an application that is hosted in the CWS and
   downloaded to the user's machine. To distribute an application as a packaged
   application, you upload the entire application, including all application
-  assets and metadata, to the CWS.
+  assets and metadata, to the CWS. Learn more on the `Chrome App </apps>`_
+  documentation page.
 
 * An **extension** is a packaged application that has a tiny UI component
   (extensions are typically used to extend the functionality of the Chrome
   browser). To distribute an application as an extension, you upload the entire
-  application, including all application assets and metadata, to the CWS.
+  application, including all application assets and metadata, to the CWS. Learn
+  more on the `Chrome extensions </extensions>`_ documentation page.
+
+The web store documentation contains a handy guide to `help you choose which to
+use <https://developer.chrome.com/webstore/choosing>`_.
 
 It's clearly not convenient to package and upload files to the Chrome Web Store
 every time you want to run a new build of your application, but there are four
 alternative techniques you can use to run the application during development.
 These techniques are listed in the following table and described in detail
 below. Each technique has certain requirements (NaCl flag, web server, and/or
 CWS metadata); these are explained in the :ref:`Requirements <requirements>`
 section below.
 
 
@@ skipping 402 matching lines @@
      be able to find the application by searching in the CWS.
 
 To publish an application to the world after publishing it to test accounts,
 you must first unpublish the application. For additional information see
 `Publishing Your App </webstore/docs/publish>`_, and in particular `Publishing
 to test accounts </webstore/publish#testaccounts>`_.
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. |extensions| image:: /images/extensions-management.png
 .. |new-tab-apps| image:: /images/new-tab-apps.png