Second batch of corrections for incorrect paths.

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>
@@ skipping 10 matching lines @@
 </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
 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
 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>
+<code>/pepper_&lt;version&gt;/examples/api/input_event</code> and
+<code>/pepper_&lt;version&gt;/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>/pepper_&lt;version&gt;/examples/demo/pi_generator</code> uses ppapi_simple to manage
+view change events and 2D graphics.</p>
 <h2 id="overview">Overview</h2>
 <p>When a user interacts with the web page using a keyboard, mouse or some other
 input device, the browser generates input events.  In a traditional web
 application, these input events are passed to and handled in JavaScript,
 typically through event listeners and event handlers. In a Native Client
 application, user interaction with an instance of a module (e.g., clicking
 inside the rectangle managed by a module) also generates input events, which
 are passed to the module. The browser also passes view change and focus events
 that affect a module&#8217;s instance to the module. Native Client modules can
 override certain functions in the <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance</a> class to handle input
@@ skipping 279 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>
 
 {{/partials.standard_nacl_api}}