Second batch of corrections for incorrect paths.

native_client_sdk/src/doc/devguide/coding/view-focus-input-events.rst

 .. _view_focus_input_events:
 
 :template: standard_nacl_api
 
 ####################################
 View Change, Focus, and Input Events
 ####################################
 
 .. contents::
   :local:
   :backlinks: none
   :depth: 2
 
 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 :doc:`Technical Overview <../../overview>`.
 
 There are two examples used in this chapter to illustrate basic
 programming techniques. The ``input_events`` example is used to
 illustrate how your module can react to keyboard and mouse input
 event.  The ``mouse_lock`` example is used to illustrate how your module
 can react to view change events. You can find these examples in the
-``/examples/api/input_events`` and ``/examples/api/mouse_lock``
-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 ``pi_generator`` example in
-``/examples/demo/pi_generator`` uses ppapi_simple to manage view
-change events and 2D graphics.
+``/pepper_<version>/examples/api/input_event`` and 
+``/pepper_<version>/examples/api/mouse_lock`` 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 ``pi_generator`` example in
+``/pepper_<version>/examples/demo/pi_generator`` uses ppapi_simple to manage
+view change events and 2D graphics.
 
 
 Overview
 ========
 
 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
@@ skipping 286 matching lines @@
 
 Threading and blocking
 ----------------------
 
 ``HandleInputEvent()`` in this example runs on the main module thread.
 However, the bulk of the work happens on a separate worker thread (see
 ``ProcessEventOnWorkerThread``). ``HandleInputEvent()`` puts events in
 the ``event_queue_`` and the worker thread takes events from the
 ``event_queue_``. This processing happens independently of the main
 thread, so as not to slow down the browser.