[NaCl SDK Docs] Add release notes for Chrome 34 and 35.

native_client_sdk/doc_generated/pepper_stable/cpp/classpp_1_1_message_loop.html

Index: native_client_sdk/doc_generated/pepper_stable/cpp/classpp_1_1_message_loop.html
diff --git a/native_client_sdk/doc_generated/pepper_stable/cpp/classpp_1_1_message_loop.html b/native_client_sdk/doc_generated/pepper_stable/cpp/classpp_1_1_message_loop.html
index 1346d7794590c2f2d3ea5e2820adb4adcfc5bb59..d78b9bf39f35de92ae8e68311c87b0ba00b4b6db 100644
--- a/native_client_sdk/doc_generated/pepper_stable/cpp/classpp_1_1_message_loop.html
+++ b/native_client_sdk/doc_generated/pepper_stable/cpp/classpp_1_1_message_loop.html
@@ -62,7 +62,7 @@ Static Public Member Functions</h2><table class="memberdecls">
 </pre></div><p> For a C++ example, see ppapi/utility/threading/simple_thread.h</p>
 <p>(You can also create the message loop resource on the background thread, but then the main thread will have no reference to it should you want to call <a class="el" href="classpp_1_1_message_loop.html#a2c24506ef8be1745d29983b2d7803e36" title="Schedules work to run on the given message loop.">PostWork()</a>).</p>
 <p>THREAD HANDLING</p>
-<p>The main thread has an implicitly created message loop. The main thread is the thread where PPP_InitializeModule and PPP_Instance functions are called. You can retrieve a reference to this message loop by calling <a class="el" href="classpp_1_1_message_loop.html#a70558dd2cfda90b4869dc9960223f7ed">GetForMainThread()</a> or, if your code is on the main thread, GetForCurrentThread() will also work.</p>
+<p>The main thread has an implicitly created message loop. The main thread is the thread where PPP_InitializeModule and PPP_Instance functions are called. You can retrieve a reference to this message loop by calling <a class="el" href="classpp_1_1_message_loop.html#a70558dd2cfda90b4869dc9960223f7ed">GetForMainThread()</a> or, if your code is on the main thread, <a class="el" href="classpp_1_1_message_loop.html#abba91f736f52838f28961a571f79f09a">GetCurrent()</a> will also work.</p>
 <p>Some special threads created by the system can not have message loops. In particular, the background thread created for audio processing has this requirement because it's intended to be highly responsive to keep up with the realtime requirements of audio processing. You can not make PPAPI calls from these threads.</p>
 <p>Once you associate a message loop with a thread, you don't have to keep a reference to it. The system will hold a reference to the message loop for as long as the thread is running. The current message loop can be retrieved using the <a class="el" href="classpp_1_1_message_loop.html#abba91f736f52838f28961a571f79f09a">GetCurrent()</a> function.</p>
 <p>It is legal to create threads in your plugin without message loops, but PPAPI calls will fail unless explicitly noted in the documentation.</p>