Per P0 reqs add launch pts + make download obvious. Also misc cpy edits.

native_client_sdk/src/doc/devguide/coding/url-loading.rst

 .. _devguide-coding-url-loading:
 
 ###########
 URL Loading
 ###########
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 Introduction
 ============
 
-This chapter describes how to use the `URLLoader API
+This section describes how to use the `URLLoader API
 </native-client/pepper_stable/cpp/classpp_1_1_u_r_l_loader>`_ to load resources
 such as images and sound files from a server into your application.
 
-The example discussed in this chapter is included in the SDK in the directory
+The example discussed in this section is included in the SDK in the directory
 ``examples/api/url_loader``.
 
 Reference information
 =====================
 
 For reference information related to loading data from URLs, see the
 following documentation:
 
 * `url_loader.h </native-client/pepper_stable/cpp/url__loader_8h>`_ - Contains
   ``URLLoader`` class for loading data from URLs
 * `url_request_info.h
   </native-client/pepper_stable/cpp/url__request__info_8h>`_ - Contains
   ``URLRequest`` class for creating and manipulating URL requests
 * `url_response_info.h
   </native-client/pepper_stable/cpp/url__response__info_8h>`_ - Contains
   ``URLResponse`` class for examaning URL responses
 
 Background
 ==========
 
 When a user launches your Native Client web application, Chrome downloads and
 caches your application'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.
 
 After you'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
 to use the `Pepper FileIO API
 </native-client/pepper_stable/cpp/classpp_1_1_file_i_o>`_ to write those assets
 to a persistent, sandboxed location on the user's file system.
 
 The ``url_loader`` example
 ==========================
@@ skipping 186 matching lines @@
 or there is an error (less than -1). ``OnRead`` is called in the event of an
 error or ``PP_OK``.
 
 Displaying a result
 -------------------
 
 OnRead calls ``ReportResultAndDie`` when either an error or ``PP_OK`` is
 returned to indicate streaming of file is complete. ``ReportResultAndDie`` then
 calls ``ReportResult,`` which calls ``PostMessage`` to send the result back to
 the HTML page.