Refresh the README.md

[mamercad]

Fix the broken Slack badge image, remove contractions, make grammar changes, write OS names and versions more consistently, show long options in commands, etc. I'll add markdown linting in another PR shortly.

[arm4b]

I'm 👍 for the Readme refresh, but 👎 for Markdown linting as that's another uneeded check that might block a PR or change.

I think markdown linting makes sense for the projects where every file is documentation, but not for a single README.md when the frequency of change is low and the chance of breaking a Markdown file is even lower (they just work!).
Let's avoid utilizing computing resources in this case 🍏

[mamercad]

I'm 👍 for the Readme refresh, but 👎 for Markdown linting as that's another uneeded check that might block a PR or change.

I think markdown linting makes sense for the projects where every file is documentation, but not for a single README.md when the frequency of change is low and the chance of breaking a Markdown file is even lower (they just work!). Let's avoid utilizing computing resources in this case 🍏

Sure, I'll push without the workflow shortly.

[mamercad]

I'm 👍 for the Readme refresh, but 👎 for Markdown linting as that's another uneeded check that might block a PR or change.
I think markdown linting makes sense for the projects where every file is documentation, but not for a single README.md when the frequency of change is low and the chance of breaking a Markdown file is even lower (they just work!). Let's avoid utilizing computing resources in this case 🍏

Sure, I'll push without the workflow shortly.

Done, I rebased as well so the history should be clean.

[mamercad]

In the spirit of not running workflows unnecessarily, I'm noticing that the build workflow is running (for this README.md update, we should probably fix that).

[arm4b]

Thanks for the refresh!