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

native_client_sdk/doc_generated/pepper_dev/cpp/classpp_1_1_instance.html

Index: native_client_sdk/doc_generated/pepper_dev/cpp/classpp_1_1_instance.html
diff --git a/native_client_sdk/doc_generated/pepper_dev/cpp/classpp_1_1_instance.html b/native_client_sdk/doc_generated/pepper_dev/cpp/classpp_1_1_instance.html
index f0ceeb48bddf43902ad0361f9d636bcebe63c893..1c78e683e0b8529b32c40722beabe9ae0d7850df 100644
--- a/native_client_sdk/doc_generated/pepper_dev/cpp/classpp_1_1_instance.html
+++ b/native_client_sdk/doc_generated/pepper_dev/cpp/classpp_1_1_instance.html
@@ -366,7 +366,7 @@ Static Public Member Functions</h2><table class="memberdecls">
 <p><a class="el" href="classpp_1_1_instance.html#a46aa2feb657fa14263a29375fe458b00" title="HandleInputEvent() handles input events from the browser.">HandleInputEvent()</a> handles input events from the browser. </p>
 <p>The default implementation does nothing and returns false.</p>
 <p>In order to receive input events, you must register for them by calling <a class="el" href="classpp_1_1_instance.html#a2e2d63280786c0cc41b7c6f656cc81b5" title="RequestInputEvents() requests that input events corresponding to the given input events are delivered...">RequestInputEvents()</a> or <a class="el" href="classpp_1_1_instance.html#a6341c14fc54427e45349f5158483e017" title="RequestFilteringInputEvents() requests that input events corresponding to the given input events are ...">RequestFilteringInputEvents()</a>. By default, no events are delivered.</p>
-<p>If the event was handled, it will not be forwarded to the web page or browser. If it was not handled, it will bubble according to the normal rules. So it is important that an instance respond accurately with whether event propagation should continue.</p>
+<p>If the event was handled, it will not be forwarded to any default handlers. If it was not handled, it may be dispatched to a default handler. So it is important that an instance respond accurately with whether event propagation should continue.</p>
 <p>Event propagation also controls focus. If you handle an event like a mouse event, typically the instance will be given focus. Returning false from a filtered event handler or not registering for an event type means that the click will be given to a lower part of the page and your instance will not receive focus. This allows an instance to be partially transparent, where clicks on the transparent areas will behave like clicks to the underlying page.</p>
 <p>In general, you should try to keep input event handling short. Especially for filtered input events, the browser or page may be blocked waiting for you to respond.</p>
 <p>The caller of this function will maintain a reference to the input event resource during this call. Unless you take a reference to the resource to hold it for later, you don't need to release it.</p>