Mojo markdown fixes

Bug: None
Change-Id: I1e86c4a52bb3f0eca8c896b5e23664ab1ca1f505
Reviewed-on: https://chromium-review.googlesource.com/1178629
Commit-Queue: Chase Phillips <cmp@chromium.org>
Reviewed-by: Ken Rockot <rockot@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583805}

mojo/README.md

@@ -46,7 +46,7 @@ This is a reasonable option when you can guarantee that all interconnected
 process binaries are linking against precisely the same revision of Mojo Core.
 To support other scenarios, use dynamic linking.
 
-## Dynamic Linking
+### Dynamic Linking
 On some platforms, it's also possible for applications to rely on a
 dynamically-linked Mojo Core library (`libmojo_core.so` or `mojo_core.dll`)
 instead of statically linking against Mojo Core.

mojo/public/cpp/system/README.md

@@ -47,7 +47,7 @@ mojo::MessagePipe pipe;
 // NOTE: Because pipes are bi-directional there is no implicit semantic
 // difference between |handle0| or |handle1| here. They're just two ends of a
 // pipe. The choice to treat one as a "client" and one as a "server" is entirely
-// a the API user's decision.
+// the API user's decision.
 mojo::ScopedMessagePipeHandle client = std::move(pipe.handle0);
 mojo::ScopedMessagePipeHandle server = std::move(pipe.handle1);
 ```
@@ -124,7 +124,7 @@ for detailed C++ data pipe API documentation.
 
 ## Shared Buffers
 
-A new shared buffers can be allocated like so:
+A new shared buffer can be allocated like so:
 
 ``` cpp
 mojo::ScopedSharedBufferHandle buffer =

mojo/public/tools/bindings/README.md

@@ -283,7 +283,7 @@ For details on how unions like this translate to generated bindings code, see
 ### Enumeration Types
 
 Enumeration types may be defined using the **enum** keyword either directly
-within a module or within the namespace of some struct or interface:
+within a module or nested within the namespace of some struct or interface:
 
 ```
 module business.mojom;
@@ -304,8 +304,8 @@ struct Employee {
 };
 ```
 
-That that similar to C-style enums, individual values may be explicitly assigned
-within an enum definition. By default values are based at zero and incremenet by
+Similar to C-style enums, individual values may be explicitly assigned within an
+enum definition. By default, values are based at zero and increment by
 1 sequentially.
 
 The effect of nested definitions on generated bindings varies depending on the
@@ -314,7 +314,7 @@ target language. See [documentation for individual target languages](#Generated-
 ### Constants
 
 Constants may be defined using the **const** keyword either directly within a
-module or within the namespace of some struct or interface:
+module or nested within the namespace of some struct or interface:
 
 ```
 module business.mojom;
@@ -341,7 +341,7 @@ target language. See [documentation for individual target languages](#Generated-
 
 An **interface** is a logical bundle of parameterized request messages. Each
 request message may optionally define a parameterized response message. Here's
-syntax to define an interface `Foo` with various kinds of requests:
+an example to define an interface `Foo` with various kinds of requests:
 
 ```
 interface Foo {