Second batch of corrections for incorrect paths.

native_client_sdk/doc_generated/devguide/coding/native-client-modules.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="native-client-modules">
 <span id="devcycle-native-client-modules"></span><h1 id="native-client-modules"><span id="devcycle-native-client-modules"></span>Native Client Modules</h1>
 <p>This document describes the classes and functions that you need to implement in
 a Native Client module in order for Chrome to load, initialize, and run it.  The
 requirements are the same regardless of whether or not the module uses PNaCl,
 but depend on whether the module is written in C or C++.</p>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
@@ skipping 105 matching lines @@
 <li>Code that defines your own Module class (derived from the <code>pp::Module</code>
 class)</li>
 <li>Code that defines your own Instance class (derived from the <code>pp:Instance</code>
 class)</li>
 </ul>
 <p>In the &#8220;Hello tutorial&#8221; example (in the <code>getting_started/part1</code> directory of
 the NaCl SDK), these three components are specified in the file
 <code>hello_tutorial.cc</code>. Here is the factory function:</p>
 <pre class="prettyprint">
 namespace pp {
-Module* CreateModule() {
-  return new HelloTutorialModule();
-}
+  Module* CreateModule() {
+    return new HelloTutorialModule();
+  }
 }
 </pre>
 <p>The <code>CreateModule()</code> factory function is the main binding point between a
 module and the browser, and serves as the entry point into the module. The
 browser calls <code>CreateModule()</code> when a module is first loaded; this function
 returns a Module object derived from the <code>pp::Module</code> class. The browser keeps
 a singleton of the Module object.</p>
 <p>Below is the Module class from the &#8220;Hello tutorial&#8221; example:</p>
 <pre class="prettyprint">
 class HelloTutorialModule : public pp::Module {
@@ skipping 27 matching lines @@
 <a class="reference internal" href="/native-client/devguide/coding/message-system.html"><em>Native Client messaging system</em></a> for more information about
 how to send messages between JavaScript code and Native Client modules.</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 documents in the
 Developer&#8217;s Guide build on these code samples and add more interesting
 functionality.</p>
 </section>
 
 {{/partials.standard_nacl_article}}