Fix typos and markdown formatting in examples

[Alejandro-Casanova]

Hi Christopher,

I'm currently reading your book and, first of all, I wanted to thank you for such a valuable contribution. It's been very insightful so far, and I'm really enjoying it.

I've also been going through the companion code examples and noticed some typos. And I thought that, as I'll be going through most of it anyway, I might as well report these to you in the form of a pull request, so you can easily correct them. I hope this doesn't come out as "nitpicky"!

I've also noticed some possible corrections and improvements to the markdown syntax. I usually follow markdownlint rules. As some of these preferences might be subjective, I'm thinking of keeping commits small so any single change can be easily rejected or edited if you see fit.

Please let me know your thoughts on this!

[ckormanyos]

Hi @Alejandro-Casanova, I'm sorry that I overlooked this PR over the holidays, as this seems to have produced an unfortunate delay.

Thank you, I really appreciate your corrections. I need to approve your CI/CD run (since first-time contributors need approval for CI/CD). It is cycling.

Docs changes usually do not influence CI/CD, but we still need to run it

Let's get this going now.

[ckormanyos]

The sonar cloud run fails because I never figured out how to let contributors run/use my SONAR TOKEN. I disabled it. It is not truly failing. It is an access rights problem.

[ckormanyos]

As some of these preferences might be subjective, I'm thinking of keeping commits small so any single change can be easily rejected or edited if you see fit.

So far, good, If you find anything else on the go, please just PR it any time.

[ckormanyos]

Merged. Many thanks @Alejandro-Casanova

[Alejandro-Casanova]

You're welcome @ckormanyos! :)