Index: native_client_sdk/doc_generated/devguide/coding/message-system.html |
diff --git a/native_client_sdk/doc_generated/devguide/coding/message-system.html b/native_client_sdk/doc_generated/devguide/coding/message-system.html |
index 87f84b3e6c5fbeac6735b86d474d15c6d75d96e1..ef09cdf3d1b4fec9fb32c590173cecf1d7c3885d 100644 |
--- a/native_client_sdk/doc_generated/devguide/coding/message-system.html |
+++ b/native_client_sdk/doc_generated/devguide/coding/message-system.html |
@@ -58,7 +58,7 @@ HandleMessage(), PostMessage())</li> |
<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’s up to |
you to decide on the type of message and define how to process the messages on |