Upstream version 10.39.225.0

[platform/framework/web/crosswalk.git] / src / native_client_sdk / doc_generated / devguide / coding / url-loading.html

diff --git a/src/native_client_sdk/doc_generated/devguide/coding/url-loading.html b/src/native_client_sdk/doc_generated/devguide/coding/url-loading.html
index 6465d5e..895dc00 100644 (file)
--- a/src/native_client_sdk/doc_generated/devguide/coding/url-loading.html
+++ b/src/native_client_sdk/doc_generated/devguide/coding/url-loading.html
@@ -22,9 +22,9 @@
 </ul>
 
 </div><h2 id="introduction">Introduction</h2>
-<p>This chapter describes how to use the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_u_r_l_loader">URLLoader API</a> to load resources
+<p>This section describes how to use the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_u_r_l_loader">URLLoader API</a> to load resources
 such as images and sound files from a server into your application.</p>
-<p>The example discussed in this chapter is included in the SDK in the directory
+<p>The example discussed in this section is included in the SDK in the directory
 <code>examples/api/url_loader</code>.</p>
 <h2 id="reference-information">Reference information</h2>
 <p>For reference information related to loading data from URLs, see the
@@ -42,7 +42,7 @@ following documentation:</p>
 caches your application&#8217;s HTML file, manifest file (.nmf), and Native Client
 module (.pexe or .nexe). If your application needs additional assets, such as
 images and sound files, it must explicitly load those assets. You can use the
-Pepper APIs described in this chapter to load assets from a URL into your
+Pepper APIs described in this section to load assets from a URL into your
 application.</p>
 <p>After you&#8217;ve loaded assets into your application, Chrome will cache those
 assets. To avoid being at the whim of the Chrome cache, however, you may want