NaCl docs: clarify Chrome apps instead of packaged apps

native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst

 ######################################
 Dynamic Linking and Loading with glibc
 ######################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 .. Note::
@@ skipping 297 matching lines @@
 
 As described above, an application's manifest file must explicitly list all the
 executable code modules that the application directly depends on, including
 modules from the application itself (.nexe and .so files), modules from the
 Native Client SDK (e.g., libppapi_cpp.so), and perhaps also modules from
 `naclports <http://code.google.com/p/naclports/>`_ or from
 `middleware systems <../../community/middleware>`_ that
 the application uses. You must provide all of those modules as part of the
 application deployment process.
 
-As explained in :doc:`Distributing Your Application
-<../distributing>`, there are two basic ways to deploy an application:
+As explained in :doc:`Distributing Your Application <../distributing>`, there
+are two basic ways to deploy a `Chrome app </apps>`_:
 
 * **hosted application:** all modules are hosted together on a web server of

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

looks like "hosted app" and "Chrome App" are the terms: see
https://developer.chrome.com/webstore/choosing

Perhaps we should remove most of this section and just reference this link?

[JF, 2015/02/10 18:26:16]

I added the link, but I think we want to keep the list.

   your choice
 
 * **packaged application:** all modules are packaged into one file, hosted in
   the Chrome Web Store, and downloaded to the user's machine
 
 You must deploy all the modules listed in your application's manifest file for
 either the hosted application or the packaged application case. For hosted
 applications, you must upload the modules to your web server. For packaged
 applications, you must include the modules in the application's Chrome Web
 Store .crx file. Modules should use URLs/names that are consistent with those
@@ skipping 95 matching lines @@
 **undefined reference to 'dlopen' collect2: ld returned 1 exit status**
   This is a linker ordering problem that usually results from improper ordering
   of command line flags when linking. Reconfigure your command line string to
   list libraries after the -o flag.
 
 .. |menu-icon| image:: /images/menu-icon.png
 .. _objdump: http://en.wikipedia.org/wiki/Objdump
 .. _GLIBC: http://www.gnu.org/software/libc/index.html
 .. _POSIX: http://en.wikipedia.org/wiki/POSIX
 .. _newlib: http://sourceware.org/newlib/