fix two typos (electron#311)

* fixed typo (one 'to' too much)

* fixed small typo

Author: jh-isw

sections/communication/ipc.html

@@ -66,7 +66,7 @@ <h5>Main Process</h5>
           </div>
           <p>It is common practice to create a new invisible browser window (renderer process) in order to run tasks without impacting performance in the main app's window.</p>
           <p>In this example we use the <code>remote</code> module to create a new invisible browser window from this renderer process. When the new page is loaded we send a message with <code>ipc</code> that the new window is listening for.</p>
-          <p>The new window then computes the factorial and sends the result to be recieved by this, the original, window and added to the page above.</p>
+          <p>The new window then computes the factorial and sends the result to be received by this, the original, window and added to the page above.</p>
           <h5>Renderer Process</h5>
           <pre><code data-path="renderer-process/communication/invisible-msg.js"></code></pre>
           <h5>Invisible Window Page HTML</h5>

sections/windows/crash-hang.html

@@ -48,7 +48,7 @@ <h5>Renderer Process</h5>
           <div class="demo-protip">
             <h2>ProTip</h2>
             <strong>Wait for the process to become responsive again.</strong>
-            <p>A third option in the case of a process that is hanging is to wait and see if the problem resolves, allowing the process to become responsive again. To to do this, use the <code>BrowserWindow</code> event 'responsive' as shown below.</p>
+            <p>A third option in the case of a process that is hanging is to wait and see if the problem resolves, allowing the process to become responsive again. To do this, use the <code>BrowserWindow</code> event 'responsive' as shown below.</p>
             <pre><code class="language-js">win.on('responsive', function () {
   // Do something when the window is responsive again
 })</code></pre>