[NaCl SDK] Remove references to naclports bundle

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

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 211aaef1ec047485329641a3f4f45263ed2cccff..3958d8aeb08ff97285ff20224078a739adf22a25 100644
--- a/native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst
+++ b/native_client_sdk/src/doc/devguide/devcycle/dynamic-loading.rst
@@ -310,9 +310,9 @@ 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.
+`webports <https://chromium.googlesource.com/webports>`_ 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 a `Chrome app </apps>`_: