Fix emacs instructions

[mmahmoudian]

Description

This PR contains the following in 2 commits:

1. fixing numerous typos
2. capitalizing Emacs word when it is not in the code
3. defining code-fence language for the code blocks to enable syntax highlighting

P.s: As for the commit messages, I tried to look-up previous commit messages and picked the style that I though is correct. Turned out (base on the next session of this PR template), I should have used fix(docs) instead of improve(docs). I hope the current messages are up to your standards. If not let me know, and I will invest some time to delete the branch and create commits with the other prefix. If that's the case, please provide me with the commit message I should use to avoid similar mistake :)

Type of Change

Changes in docs (docs)

• ✨ improve(docs) - e.g. added a new paragraph, example, using a better wording, adding a new document, etc.
• 🛠️ fix(docs) - bug fix, e.g. fix a typo, page render issue
• ❌ BREAKING CHANGE(docs) - e.g. removing a document/article/category that was referenced in many other places
• 🧹 refactor(docs) - changed a code example, e.g. replaced old code with a modern one
• 🗑️ chore(docs) - other changes that don't affect the docs, e.g. updating the CI/CD pipeline

Changes in the platform (platform)

• ✨ feat(platform) - a new feature, e.g. a new MDX component, plugin, theme, etc.
• 🛠️ fix(platform) - bug fix, e.g. fix a typo, issue causing component to crash
• ❌ BREAKING CHANGE(platform) - e.g. removing a feature, changing the API, etc.
• 🧹 refactor(platform) - code improvements, changes, e.g. unifying style, renaming internals, etc.
• 📝 docs(platform) - updated code documentation
• 🗑️ chore(platform) - other changes that don't affect the platform directly, e.g. updating the CI/CD pipeline

[Dich0tomy]

LGTM! Thank you! :)