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

native_client_sdk/doc_generated/devguide/coding/view-focus-input-events.html

 {{+bindTo:partials.standard_nacl_api}}
 
 <section id="view-change-focus-and-input-events">
 <h1 id="view-change-focus-and-input-events">View Change, Focus, and Input Events</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#overview" id="id2">Overview</a></li>
 <li><p class="first"><a class="reference internal" href="#handling-browser-events" id="id3">Handling browser events</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#didchangeview" id="id4">DidChangeView()</a></li>
 <li><a class="reference internal" href="#didchangefocus" id="id5">DidChangeFocus()</a></li>
 </ul>
 </li>
 <li><p class="first"><a class="reference internal" href="#handling-input-events" id="id6">Handling input events</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#registering-a-module-to-accept-input-events" id="id7">Registering a module to accept input events</a></li>
 <li><a class="reference internal" href="#determining-and-branching-on-event-types" id="id8">Determining and branching on event types</a></li>
 <li><a class="reference internal" href="#threading-and-blocking" id="id9">Threading and blocking</a></li>
 </ul>
 </li>
 </ul>
 
-</div><p>This chapter describes view change, focus, and input event handling for a
-Native Client module. The chapter assumes you are familiar with the
+</div><p>This section describes view change, focus, and input event handling for a
+Native Client module. 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>
-<p>There are two examples used in this chapter to illustrate basic
+<p>There are two examples used in this section to illustrate basic
 programming techniques. The <code>input_events</code> example is used to
 illustrate how your module can react to keyboard and mouse input
 event.  The <code>mouse_lock</code> example is used to illustrate how your module
 can react to view change events. You can find these examples in the
 <code>/examples/api/input_events</code> and <code>/examples/api/mouse_lock</code>
 directories in the Native Client SDK.  There is also the
 ppapi_simple library that can be used to to implement most of the
 boiler plate.  The <code>pi_generator</code> example in
 <code>/examples/demo/pi_generator</code> uses ppapi_simple to manage view
 change events and 2D graphics.</p>
@@ skipping 297 matching lines @@
 <h3 id="threading-and-blocking">Threading and blocking</h3>
 <p><code>HandleInputEvent()</code> in this example runs on the main module thread.
 However, the bulk of the work happens on a separate worker thread (see
 <code>ProcessEventOnWorkerThread</code>). <code>HandleInputEvent()</code> puts events in
 the <code>event_queue_</code> and the worker thread takes events from the
 <code>event_queue_</code>. This processing happens independently of the main
 thread, so as not to slow down the browser.</p>
 </section></section></section>
 
 {{/partials.standard_nacl_api}}