NaCl docs: clarify Chrome apps instead of packaged apps

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

Index: native_client_sdk/src/doc/devguide/devcycle/running.rst
diff --git a/native_client_sdk/src/doc/devguide/devcycle/running.rst b/native_client_sdk/src/doc/devguide/devcycle/running.rst
index 792b323b73b5a97da2376f5f4c3271fb18ee1097..f9bea2222e68a8dab5ec790d6f5f83ca871fe027 100644
--- a/native_client_sdk/src/doc/devguide/devcycle/running.rst
+++ b/native_client_sdk/src/doc/devguide/devcycle/running.rst
@@ -45,17 +45,20 @@ 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

[binji, 2015/02/10 17:49:40]

same here

   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.
 
 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