| 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 2bbe720809cdc862d544c8218c8c7ceb4ee70bf0..c07032df33476183969d30110cbddabd32902339 100644
|
| --- a/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html
|
| +++ b/native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html
|
| @@ -318,7 +318,7 @@ 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 (.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="naclports_">naclport</a> or from <a class="reference internal" href="/native-client/community/middleware.html"><em>middleware systems</em></a> that
|
| +<a class="reference external" href="naclports_">naclport</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>
|
|
|