Fix Markdown Syntax issues in IPC docs

Bug: None
Change-Id: I059661fde35652c0fc867bcc60b02bfad3e178d6
Reviewed-on: https://chromium-review.googlesource.com/1026488
Reviewed-by: Tom Sepez <tsepez@chromium.org>
Commit-Queue: Ryan Sleevi <rsleevi@chromium.org>
Cr-Commit-Position: refs/heads/master@{#553637}

Author: sleevi

ipc/README.md

@@ -369,13 +369,11 @@ it.
 
 Depending on what resources you need access to, the main classes are:
 
-| Renderer Class  | Corresponding Browser Class |  Explanation                                                                                                      |
-|-----------------|-----------------------------|-------------------------------------------------------------------------------------------------------------------|
-| `RenderFrame`   | `RenderFrameHost`           |  A single frame. Use this for frame-to-frame messages.                                                            |
-| `RenderView`    | `RenderViewHost`            | A view (conceptually a 'tab'). You cannot send Mojo messages to a `RenderView` directly, since frames in a tab can
-                                                  be in multiple processes (and the classes are deprecated). Migrate these to `RenderFrame` instead, or see section
-                                                  [Migrating IPC calls to `RenderView` or `RenderViewHost`](#UMigrating-IPC-calls-to-RenderView-or-RenderViewHost). |
-| `RenderProcess` | `RenderProcessHost`         | A process, containing multiple frames (probably from the same origin, but not always).                            |
+| Renderer Class  | Corresponding Browser Class |  Explanation                                                                                                       |
+|-----------------|-----------------------------|--------------------------------------------------------------------------------------------------------------------|
+| `RenderFrame`   | `RenderFrameHost`           |  A single frame. Use this for frame-to-frame messages.                                                             |
+| `RenderView`    | `RenderViewHost`            | A view (conceptually a 'tab'). You cannot send Mojo messages to a `RenderView` directly, since frames in a tab can be in multiple processes (and the classes are deprecated). Migrate these to `RenderFrame` instead, or see section [Migrating IPC calls to `RenderView` or `RenderViewHost`](#UMigrating-IPC-calls-to-RenderView-or-RenderViewHost).  |
+| `RenderProcess` | `RenderProcessHost`         | A process, containing multiple frames (probably from the same origin, but not always).                             |
 
 **NOTE:** Previously, classes that ended with `Host` were implemented on the
 browser side; the equivalent classes on the renderer side had the same name
@@ -719,7 +717,6 @@ the wire format used is defined entirely by `IPC::ParamTraits<T>` for whatever
 `foo::mojom::MyGiganticStructure` to `foo::MyGiganticStructure`, your typemap
 must point to some header which defines
 `IPC::ParamTraits<foo::MyGiganticStructure>`.
-```
 
 There are several examples of this traits implementation in common IPC traits
 defined [here](https://code.google.com/p/chromium/codesearch#chromium/src/ipc/ipc_message_utils.h).