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 0c525b1e2543846de4d2fef196b17450a4780ca4..5ee1f1ad06e1575c4f3c21d2858f2de60fa4bb46 100644 |
--- a/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html |
+++ b/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html |
@@ -316,8 +316,9 @@ the list of shared library dependencies using tools such as <code>objdump_</code |
executable code modules that the application directly depends on, including |
modules from the application itself (<code>.nexe</code> and <code>.so</code> files), modules from |
the Native Client SDK (e.g., <code>libppapi_cpp.so</code>), 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> |
+<a class="reference external" href="https://chromium.googlesource.com/webports">webports</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 a <a class="reference external" href="/apps">Chrome app</a>:</p> |
<ul class="small-gap"> |