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

native_client_sdk/doc_generated/pepper_stable/c/struct_p_p_b___input_event__1__0.html

Index: native_client_sdk/doc_generated/pepper_stable/c/struct_p_p_b___input_event__1__0.html
diff --git a/native_client_sdk/doc_generated/pepper_stable/c/struct_p_p_b___input_event__1__0.html b/native_client_sdk/doc_generated/pepper_stable/c/struct_p_p_b___input_event__1__0.html
index 92417df8ae62d27cb940cacd27883bf43a4275f1..d4739b9a779ba15be85947e62992b836be06382c 100644
--- a/native_client_sdk/doc_generated/pepper_stable/c/struct_p_p_b___input_event__1__0.html
+++ b/native_client_sdk/doc_generated/pepper_stable/c/struct_p_p_b___input_event__1__0.html
@@ -161,7 +161,7 @@ Data Fields</h2><table class="memberdecls">
 <p>It's recommended that you use <a class="el" href="struct_p_p_b___input_event__1__0.html#a42dcc8edf80141680e919258f3066069" title="RequestFilteringInputEvents() requests that input events corresponding to the given input events are ...">RequestFilteringInputEvents()</a> for keyboard events instead of this function so that you don't interfere with normal browser accelerators.</p>
 <p>By default, no input events are delivered. Call this function with the classes of events you are interested in to have them be delivered to the instance. Calling this function will override any previous setting for each specified class of input events (for example, if you previously called <a class="el" href="struct_p_p_b___input_event__1__0.html#a42dcc8edf80141680e919258f3066069" title="RequestFilteringInputEvents() requests that input events corresponding to the given input events are ...">RequestFilteringInputEvents()</a>, this function will set those events to non-filtering mode).</p>
 <p>Input events may have high overhead, so you should only request input events that your plugin will actually handle. For example, the browser may do optimizations for scroll or touch events that can be processed substantially faster if it knows there are no non-default receivers for that message. Requesting that such messages be delivered, even if they are processed very quickly, may have a noticeable effect on the performance of the page.</p>
-<p>Note that synthetic mouse events will be generated from touch events if (and only if) the you do not request touch events.</p>
+<p>Note that synthetic mouse events will be generated from touch events if (and only if) you do not request touch events.</p>
 <p>When requesting input events through this function, the events will be delivered and <em>not</em> bubbled to the page. This means that even if you aren't interested in the message, no other parts of the page will get a crack at the message.</p>
 <p><b>Example:</b> </p>
 <div class="fragment"><pre class="fragment">   <a class="code" href="struct_p_p_b___input_event__1__0.html#a369d79730ad84d0b8dee9127c114086e" title="RequestInputEvent() requests that input events corresponding to the given input events are delivered ...">RequestInputEvents</a>(instance, <a class="code" href="group___enums.html#ggafe68e3c1031daa4a6496845ff47649cda79ccc5180eb39c52ab3207f0c876dd52" title="Request mouse input events.">PP_INPUTEVENT_CLASS_MOUSE</a>);