Docs - Reconcile Jekyll, Kramdown, GFM formatting

[alishamayor]

• Fixed most of the broken formatting on GitHub Pages
• Docs should now render correctly on both GitHub and GitHub Pages
• Also did a mass spellcheck

---

Notes

Our documentation lives on a GitHub Pages site, which is generated using Jekyll. Jekyll uses the Liquid templating language to process templates, and Liquid objects and variables are denoted by double curly braces: {{ }}.

Therefore, any fenced code blocks containing Ansible expressions or other phrases in {{ curly braces }} need to be wrapped with these escape tags to avoid being parsed as Liquid template tags:

<!-- {% raw %} -->
...
<!-- {% endraw %} -->

Including them as HTML-style comments ensures they don't appear on the Markdown page either.
See ARCHITECTURE.md#L36 for an example.

Jekyll also uses Kramdown to render Markdown, which is just different enough from GitHub-flavored Markdown. 🙃 There's updated HTML creating the show/hide disclosures in EXAMPLES.md, which now render code blocks and syntax-highlighting. Also, < and > need to be escaped inside the HTML blocks, which fixes #314.

I tried to minimize the complexity. As long as future content follows the same inline HTML formatting scheme, we're golden. 🚀

[alishamayor]

Using admin privilege to merge 🤓