docs: style/formatting improvements for using ibc-go > overview

[crodriguezvega]

Description

This is the first of (probably) many PRs I will try to open to unify a bit the style of our docs following the recommendations of Google's developer documentation style guide. Jeez, I wish there was a linter for this...

closes: #XXXX

Commit Message / Changelog Entry

type: commit message

see the guidelines for commit messages. (view raw markdown for examples).

---

Before we can merge this PR, please make sure that all the following items have been
checked off. If any of the checklist items are not applicable, please leave them but
write a little note why.

• Targeted PR against the correct branch (see CONTRIBUTING.md).
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the module structure standards and Go style guide.
• Wrote unit and integration tests.
• Updated relevant documentation (docs/) or specification (x/<module>/spec/).
• Added relevant godoc comments.
• Provide a commit message to be used for the changelog entry in the PR description for review.
• Re-reviewed Files changed in the Github PR explorer.
• Review Codecov Report in the comment section below once CI passes.

[damiannolan]

Nice improvements @crodriguezvega! 🚀

[DimitrisJim]

seems like an sisyphian uphill battle 😅, maybe we should at least link the google style guide in the contributing guidelines someplace?

[crodriguezvega]

seems like an sisyphian uphill battle 😅, maybe we should at least link the google style guide in the contributing guidelines someplace?

Sisyphos was a sissy compared to me, man. 😜
Yeap, we already do! :)

[DimitrisJim]

Sisyphos was a sissy compared to me, man. 😜

HAHA, absolutely destroyed.