Index: native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst |
diff --git a/native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst b/native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst |
index 5c394cabecffe917f7357fd33654b1f805bfb770..3b8dbee328fb128b5c12da6e71d5b64763bbf21e 100644 |
--- a/native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst |
+++ b/native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst |
@@ -307,7 +307,8 @@ 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 |
-`naclport <naclports_>`_ or from `middleware systems <../../community/middleware>`_ that |
+`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. |