Index: native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html |
diff --git a/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html b/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html |
index 1123f9e91588216ffb5351b005813f57f1dfb0f9..bde770956129ccdff4f24dae33ac7ec84c32e325 100644 |
--- a/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html |
+++ b/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html |
@@ -320,7 +320,8 @@ Native Client SDK (e.g., libppapi_cpp.so), and perhaps also modules 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> |