NaCL docs: add missing generated files

native_client_sdk/doc_generated/devguide/coding/message-system.html

 {{+bindTo:partials.standard_nacl_article}}
 
 <section id="messaging-system">
 <span id="message-system"></span><h1 id="messaging-system"><span id="message-system"></span>Messaging System</h1>
 <div class="contents local" id="contents" style="display: none">
 <ul class="small-gap">
 <li><a class="reference internal" href="#reference-information" id="id2">Reference information</a></li>
 <li><p class="first"><a class="reference internal" href="#introduction-to-the-messaging-system" id="id3">Introduction to the messaging system</a></p>
 <ul class="small-gap">
 <li><a class="reference internal" href="#design-of-the-messaging-system" id="id4">Design of the messaging system</a></li>
@@ skipping 40 matching lines @@
 <li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_instance">pp::Instance class</a>
 HandleMessage(), PostMessage())</li>
 <li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_module">pp::Module class</a></li>
 <li><a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_var">pp::Var class</a></li>
 </ul>
 </section><section id="introduction-to-the-messaging-system">
 <h2 id="introduction-to-the-messaging-system">Introduction to the messaging system</h2>
 <p>Native Client modules and JavaScript communicate by sending messages to each
 other. The most basic form of a message is a string.  Messages support many
 JavaScript types, including ints, arrays, array buffers, and dictionaries (see
-<a class="reference external" href="h/native-client/pepper_stable/cpp/classpp_1_1_var">pp::Var</a>,
+<a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_var">pp::Var</a>,
 <a class="reference external" href="/native-client/pepper_stable/cpp/classpp_1_1_var_array_buffer">pp:VarArrayBuffer</a>, and the
 general <a class="reference external" href="/native-client/pepper_stable/c/struct_p_p_b___messaging__1__0">messaging system documentation</a>).  It&#8217;s up to
 you to decide on the type of message and define how to process the messages on
 both the JavaScript and Native Client side. For the &#8220;Hello, World&#8221; example, we
 will work with string-typed messages only.</p>
 <p>When JavaScript posts a message to the Native Client module, the
 Pepper <code>HandleMessage()</code> function is invoked on the module
 side. Similarly, the Native Client module can post a message to
 JavaScript, and this message triggers a JavaScript event listener for
 <code>message</code> events in the DOM. (See the W3C specification on
@@ skipping 294 matching lines @@
     pp::VarArray keys = dictionary.GetKeys();
     // ...
   } else {
     // ...
   }
 }
 </pre>
 </section></section></section>
 
 {{/partials.standard_nacl_article}}