Various formatting tweaks

[murtyjones]

No description provided.

[mention-bot]

@murtyjones, thanks for your PR! By analyzing the history of the files in this pull request, we identified @aakselrod, @Roasbeef and @michielbdejong to be potential reviewers.

[Roasbeef]

Really scratching my head as to how all this shifted from under us. Everything displayed correctly until a few days ago...

There're likely other spots in our documentation that now have invalid markdown, think you could take a quick sweep and add additional commits to this PR fixing the other occurrences (if any)? Thanks!

[Roasbeef]

I'm guessing the breakage in our formatting has to do with shifts in the parser when meeting compliance with Github's new formal markdown spec.

[coveralls]

Coverage increased (+0.008%) to 69.034% when pulling 0629490 on murtyjones:patch-1 into 1efbaee on lightningnetwork:master.

[coveralls]

Coverage increased (+0.008%) to 69.034% when pulling 4630229 on murtyjones:patch-1 into 1efbaee on lightningnetwork:master.

[coveralls]

Coverage remained the same at 69.026% when pulling 4630229 on murtyjones:patch-1 into 1efbaee on lightningnetwork:master.

[coveralls]

Coverage remained the same at 69.026% when pulling 9a1e9df on murtyjones:patch-1 into 1efbaee on lightningnetwork:master.

[murtyjones]

@Roasbeef Took a pass through everything - looks good for the most part but added some things I came across.

[coveralls]

Coverage increased (+0.008%) to 69.034% when pulling 3469413 on murtyjones:patch-1 into 1efbaee on lightningnetwork:master.

[Roasbeef]

Thanks for the formatting fixes!

LGTM 👾