NaCl docs: clarify Chrome apps instead of packaged apps

native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="dynamic-linking-and-loading-with-glibc">
 <h1 id="dynamic-linking-and-loading-with-glibc">Dynamic Linking and Loading with glibc</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#c-standard-libraries-glibc-and-newlib" id="id1">C standard libraries: glibc and newlib</a></li>
 <li><a class="reference internal" href="#sdk-toolchains" id="id2">SDK toolchains</a></li>
 <li><p class="first"><a class="reference internal" href="#specifying-and-delivering-shared-libraries" id="id3">Specifying and delivering shared libraries</a></p>
 <ul class="small-gap">
@@ skipping 302 matching lines @@
 the list of shared library dependencies using tools such as <code>objdump_</code>.</p>
 <h3 id="deploying-a-dynamically-linked-application">Deploying a dynamically linked application</h3>
 <p>As described above, an application&#8217;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
 <a class="reference external" href="http://code.google.com/p/naclports/">naclports</a> or from
 <a class="reference external" href="../../community/middleware">middleware systems</a> that
 the application uses. You must provide all of those modules as part of the
 application deployment process.</p>
-<p>As explained in <a class="reference internal" href="/native-client/devguide/distributing.html"><em>Distributing Your Application</em></a>, there are two basic ways to deploy an application:</p>
+<p>As explained in <a class="reference internal" href="/native-client/devguide/distributing.html"><em>Distributing Your Application</em></a>, there
+are two basic ways to deploy a <a class="reference external" href="/apps">Chrome app</a>:</p>
 <ul class="small-gap">
 <li><strong>hosted application:</strong> all modules are hosted together on a web server of
 your choice</li>
 <li><strong>packaged application:</strong> all modules are packaged into one file, hosted in
 the Chrome Web Store, and downloaded to the user&#8217;s machine</li>
 </ul>
 <p>You must deploy all the modules listed in your application&#8217;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&#8217;s Chrome Web
@@ skipping 77 matching lines @@
 in the .nmf file &#8211; either the files are the wrong type or kind, or an
 expected library is missing.</dd>
 <dt><strong>undefined reference to &#8216;dlopen&#8217; collect2: ld returned 1 exit status</strong></dt>
 <dd>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.</dd>
 </dl>
 </section>
 
 {{/partials.standard_nacl_article}}