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

native_client_sdk/src/doc/devguide/coding/application-structure.rst

 .. _devcycle-application-structure:
 
 #####################
 Application Structure
 #####################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
-This chapter of the Developer's Guide describes the general structure of a
-Native Client application. The chapter assumes you are familiar with the
+This section of the Developer's Guide describes the general structure of a
+Native Client application. The section assumes you are familiar with the
 material presented in the :doc:`Technical Overview <../../overview>`.
 
 
 .. Note::
   :class: note
 
   The "Hello, World" example is used here to illustrate basic
   Native Client programming techniques. You can find this code in the
   */getting_started/part1* directory in the Native Client SDK download.
 
@@ skipping 219 matching lines @@
 The NaCl code is only invoked to handle various browser-issued
 events and callbacks. There is no need to shut down the NaCl instance by
 calling the ``exit()`` function. NaCl modules will be shut down when the user
 leaves the web page, or the NaCl module's ``<embed>`` is otherwise destroyed.
 If the NaCl module does call the ``exit()`` function, the instance will
 issue a ``crash`` event
 :doc:`which can be handled in Javascript<progress-events>`.
 
 While the ``CreateModule()`` factory function, the ``Module`` class, and the
 ``Instance`` class are required for a Native Client application, the code
-samples shown above don't actually do anything. Subsequent chapters in the
+samples shown above don't actually do anything. Subsequent sections in the
 Developer's Guide build on these code samples and add more interesting
 functionality.