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

native_client_sdk/doc_generated/devguide/coding/application-structure.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="application-structure">
 <span id="devcycle-application-structure"></span><h1 id="application-structure"><span id="devcycle-application-structure"></span>Application Structure</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#application-components" id="id1">Application components</a></li>
 <li><a class="reference internal" href="#html-file-and-the-embed-element" id="id2">HTML file and the &lt;embed&gt; element</a></li>
 <li><a class="reference internal" href="#manifest-files" id="id3">Manifest Files</a></li>
 <li><a class="reference internal" href="#modules-and-instances" id="id4">Modules and instances</a></li>
 <li><a class="reference internal" href="#native-client-modules-a-closer-look" id="id5">Native Client modules: A closer look</a></li>
 </ul>
 
-</div><p>This chapter of the Developer&#8217;s Guide describes the general structure of a
-Native Client application. The chapter assumes you are familiar with the
+</div><p>This section of the Developer&#8217;s Guide describes the general structure of a
+Native Client application. The section assumes you are familiar with the
 material presented in the <a class="reference internal" href="/native-client/overview.html"><em>Technical Overview</em></a>.</p>
 <aside class="note">
 The &#8220;Hello, World&#8221; example is used here to illustrate basic
 Native Client programming techniques. You can find this code in the
 <em>/getting_started/part1</em> directory in the Native Client SDK download.
 </aside>
 <h2 id="application-components">Application components</h2>
 <p>A Native Client application typically contains the following components:</p>
 <ul class="small-gap">
 <li>an HTML file;</li>
@@ skipping 171 matching lines @@
 how to send messages between JavaScript code and Native Client modules.</p>
 <p>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 <code>exit()</code> function. NaCl modules will be shut down when the user
 leaves the web page, or the NaCl module&#8217;s <code>&lt;embed&gt;</code> is otherwise destroyed.
 If the NaCl module does call the <code>exit()</code> function, the instance will
 issue a <code>crash</code> event
 <a class="reference internal" href="/native-client/devguide/coding/progress-events.html"><em>which can be handled in Javascript</em></a>.</p>
 <p>While the <code>CreateModule()</code> factory function, the <code>Module</code> class, and the
 <code>Instance</code> class are required for a Native Client application, the code
-samples shown above don&#8217;t actually do anything. Subsequent chapters in the
+samples shown above don&#8217;t actually do anything. Subsequent sections in the
 Developer&#8217;s Guide build on these code samples and add more interesting
 functionality.</p>
 </section>
 
 {{/partials.standard_nacl_article}}