Second batch of corrections for incorrect paths.

native_client_sdk/doc_generated/devguide/devcycle/dynamic-loading.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="dynamic-linking-and-loading-with-glibc">
 <h1 id="dynamic-linking-and-loading-with-glibc">Dynamic Linking and Loading with glibc</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><p class="first"><a class="reference internal" href="#introduction" id="id1">Introduction</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#c-standard-libraries-glibc-and-newlib" id="id2">C standard libraries: glibc and newlib</a></li>
 <li><a class="reference internal" href="#sdk-toolchains" id="id3">SDK toolchains</a></li>
@@ skipping 88 matching lines @@
 This could significantly reduce download size and provide a further potential
 performance benefit (for example, the hello_world example would only require
 downloading a .nexe file that&#8217;s on the order of 30KB, rather than a .nexe
 file and several libraries, which are on the order of 1.5MB).</li>
 </ul>
 <p>Native Client support for dynamic linking and loading is based on glibc. Thus,
 <strong>if your Native Client application must dynamically link and load code (e.g.,
 due to licensing considerations), we recommend that you use the glibc
 library.</strong></p>
 <aside class="note">
-<p><strong>Notes:</strong></p>
+<p><strong>Disclaimer:</strong></p>
 <ul class="small-gap">
 <li><strong>None of the above constitutes legal advice, or a description of the legal
 obligations you need to fulfill in order to be compliant with the LGPL or
 newlib licenses. The above description is only a technical explanation of
 the differences between newlib and glibc, and the choice you must make
 between the two libraries.</strong></li>
+</ul>
+
+</aside>
+<aside class="note">
+<p><strong>Notes:</strong></p>
+<ul class="small-gap">
 <li>Static linking with glibc is rarely used. Use this feature with caution.</li>
 <li>The standard C++ runtime in Native Client is provided by libstdc++; this
 library is independent from and layered on top of glibc. Because of
 licensing restrictions, libstdc++ must be statically linked for commercial
 uses, even if the rest of an application is dynamically linked.</li>
 </ul>
 
 </aside>
 <h3 id="sdk-toolchains">SDK toolchains</h3>
 <p>The Native Client SDK contains multiple toolchains, which are differentiated by
@@ skipping 280 matching lines @@
 in the .nmf file &#8211; either the files are the wrong type or kind, or an
 expected library is missing.</dd>
 <dt><strong>undefined reference to &#8216;dlopen&#8217; collect2: ld returned 1 exit status</strong></dt>
 <dd>This is a linker ordering problem that usually results from improper ordering
 of command line flags when linking. Reconfigure your command line string to
 list libraries after the -o flag.</dd>
 </dl>
 </section>
 
 {{/partials.standard_nacl_article}}