[mojo-doc] Tiny nits

docs/mojo_in_chromium.md

 # Mojo in Chromium
 
 This document is intended to serve as a Mojo primer for Chromium developers. No
 prior knowledge of Mojo is assumed.
 
 [TOC]
 
 ## Should I Bother Reading This?
 
 If you're planning to build a Chromium feature that needs IPC and you aren't
@@ skipping 31 matching lines @@
 is likely to be the most common usage encountered by Chromium developers.
 
 ### Message Pipes
 
 A message pipe is a lightweight primitive for reliable bidirectional transfer of
 relatively small packets of data. Unsurprisingly a pipe has two endpoints, and
 either endpoint may be transferred over another message pipe.
 
 Because we bootstrap a primordial message pipe between the browser process and
 each child process, this in turn means that you can create a new pipe and
-ultimately send either end to any any process, and the two ends will still be
+ultimately send either end to any process, and the two ends will still be
 able to talk to each other seamlessly and exclusively. Goodbye, routing IDs!
 
-While message pipes can carry arbitrary packets of unstructured data, we
+While message pipes can carry arbitrary packets of unstructured data we
 generally use them in conjunction with generated bindings to ensure a
 consistent, well-defined, versioned message structure on all endpoints.
 
 ### Mojom
 
 Mojom is the IDL for Mojo interfaces. Given a `.mojom` file, the bindings
 generator outputs bindings for all three of the currently supported languages.
 
 For example:
 
@@ skipping 104 matching lines @@
 
 ```
 frob:mojom::FrobinatorPtr frobinator;
 frob::FrobinatorImpl impl(GetProxy(&frobinator));
 
 // Tada!
 frobinator->Frobinate();
 ```
 
 Behind the scenes this serializes a message corresponding to the `Frobinate`
-request and writes it to one end of the pipe. Eventually (and, incidentally,
+request and writes it to one end of the pipe. Eventually (and incidentally,
 very soon after), `impl`'s internal `mojo::Binding` will decode this message and
 dispatch a call to `impl.Frobinate()`.
 
 ### Responding to Requests
 
 A common idiom in Chromium IPC is to keep track of IPC requests with some kind
 of opaque identifier (i.e. an integer *request ID*) so that you can later
 respond to a specific request using some nominally related message in the other
 direction.
 
@@ skipping 138 matching lines @@
 
 This is a work in progress. TL;DR: We'll also soon begin using Mojo services
 from Blink so that the platform layer can consume browser services
 directly via Mojo. The long-term goal there is to eliminate `content/renderer`.
 
 ## Questions, Discussion, etc.
 
 A good place to find highly concentrated doses of people who know and care
 about Mojo in Chromium would be the [chromium-mojo](https://goo.gl/A4ebWB)
 mailing list[.](https://goo.gl/L70ihQ)