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

native_client_sdk/doc_generated/devguide/coding/progress-events.html

 {{+bindTo:partials.standard_nacl_api}}
 
 <section id="progress-events">
 <h1 id="progress-events">Progress Events</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#module-loading-and-progress-events" id="id3">Module loading and progress events</a></li>
 <li><a class="reference internal" href="#handling-progress-events" id="id4">Handling progress events</a></li>
 <li><a class="reference internal" href="#displaying-load-status" id="id5">Displaying load status</a></li>
 <li><a class="reference internal" href="#the-lasterror-attribute" id="id6">The <code>lastError</code> attribute</a></li>
 <li><a class="reference internal" href="#the-readystate-attribute" id="id7">The <code>readyState</code> attribute</a></li>
 <li><a class="reference internal" href="#the-exitstatus-attribute" id="id8">The <code>exitStatus</code> attribute</a></li>
 </ul>
 
 </div><p>There are five types of events that developers can respond to in Native Client:
 progress, message, view change, focus, and input events (each described in the
-glossary below). This chapter describes how to monitor progress events (events
+glossary below). This section describes how to monitor progress events (events
 that occur during the loading and execution of a Native Client module). This
-chapter assumes you are familiar with the material presented in 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 load_progress example illustrates progress event handling. You can find
 this code in the <code>/pepper_&lt;version&gt;/examples/tutorial/load_progress/</code>
 directory in the Native Client SDK download.
 </aside>
 <h2 id="module-loading-and-progress-events">Module loading and progress events</h2>
 <p>The Native Client runtime reports a set of state changes during the module
 loading process by means of DOM progress events. This set of events is a direct
 port of the proposed W3C <a class="reference external" href="http://www.w3.org/TR/progress-events/">Progress Events</a> standard (except for the <code>crash</code>
@@ skipping 389 matching lines @@
 <code>n</code> (between 0 and 255).</li>
 <li>In the case of crashes and calls to <code>abort()</code>, the numeric value will
 be non-zero, but the exact value will depend on the chosen libc and the
 target architecture, and may change in the future. Applications should not
 rely on the <code>exitStatus</code> value being stable in these cases, but the value
 may nevertheless be useful for temporary debugging.</li>
 </ul>
 </section>
 
 {{/partials.standard_nacl_api}}