Merge developer guide formatting issues

[nineinchnick]

Description

The merge developer guide has some formatting issues and some mismatches with the API. This PR fixes them and applies the Google style guide, checked using the Vale linter.

Additional context and related issues

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

[nineinchnick]

@djsstarburst @electrum please review, especially the first two commits. @mosabua please review the last two commits (style).

[djsagain]

Thanks for doing this; the changes look fine.

I was under the impression that two spaces were required between a period and the start of the next sentence, so the change to make it a single space surprises me.

[nineinchnick]

I was under the impression that two spaces were required between a period and the start of the next sentence, so the change to make it a single space surprises me.

Yeah, it was weirdly consistent 😄 I don't think it's required though, other docs don't use it.

[mosabua]

Nice!

[mosabua]

Nice! This could be merged as is or with the commits collapsed .. either works for me.

[mosabua]

Thanks for doing this; the changes look fine.

I was under the impression that two spaces were required between a period and the start of the next sentence, so the change to make it a single space surprises me.

The two spaces are NOT required. The rendering pipeline for the output collapsed them into one. The usage of two spaces dates back to typewriter and fixed-width fonts only usage, don't do that anymore these days please..

[electrum]

Generally looks good. Thanks for improving this.