*: fix errors reported by languagetool

[SethFalco]

Inspired by: #5848

This only does the English files, LanguageTool does support other languages, but I can't manually review the suggestions.
I dumped only lines starting with > or - from the English files into a single file to save time.

The following is a non-exhaustive list of the changes made to the repository.

Notable Changes

Hyphenated Words or Redundant Spaces

• human readable -> human-readable
• Un-select -> Unselect
• time scale -> timescale
• user name -> username

Fixed Nouns

• wifi / WiFi -> Wi-Fi
• tetris -> Tetris
• coachdb -> CoachDB
• heroku -> Heroku
• monday -> Monday
• friday -> Friday
• vue -> Vue

Fixed Acronyms

• url -> URL
• uri -> URI
• usb -> USB
• instances like pdf, png, jpg, xml, css, html, etc.
• instances like cpu, ram, etc

Typos

• pathames -> pathnames
• parseable -> parsable

Misc Errors

• its vs it's
• an vs a
• singular vs plural
• double words (ie and and, or the the)
• inserting the word "the" ie "the largest", or "the highest", etc

Redundancies

These technically aren't incorrect, just longer than it needs to be.

• all of the -> all the
• short summary -> summary (short is inferred)
• in order to -> to

Ignored

The following I ignored on purpose, feel free to drop opinions on them.

British vs American English

I also ignored locale-specific reports like British vs American English as discussed on Matrix. (More Info)

False Positives

It's common to refer to things like npm in lowercase even though it's technically an acronym. This makes LanguageTool mad since it thinks it's an actual word. ie a npm package vs an npm package. It thinks "a npm package" is correct, but because we mean "a NPM package" it should be "an npm package".

---

I decided to be terrible and fixed another thing on the side in this PR.
There was a command that had extra spaces between arguments, so I also removed that. Nothing to do with LanguageTool.

• pages/common/acme.sh-dns.md

[bl-ue]

Wow, this is some really superb work — the most ultimate height of typo-fixing that I could have ever imagined 🚀🚀🚀

[bl-ue]

Here are my opinions regarding your ignored changes (in a nutshell, don't ignore any of them!):

instances like pdf, psd, png, jpg, xml, css, html, etc. Technically, when used on its own it should be uppercase.

I think we should definitely uppercase these.

instances like cpu, ram, gpu, psu, etc. (These should definitely be uppercase.)

Uppercase these too.

all of the -> all the

This has tricked me alot, I think we should use "all the"

short summary -> summary (short is inferred)

Definitely.

in order to -> to

Yep, too wordy is beating around the bush.

[bl-ue]

@SethFalco maybe also normalize eg. → e.g.?

[SethFalco]

I'll stop with the commit spam now. I've applied most of the feedback, and some of the things that I remember skipping before.
Later I'll look at LanguageTool again and see what else it was complaining about.

[bl-ue]

Now why'd you call your branch im-dead 😆

[SethFalco]

Now why'd you call your branch im-dead laughing

Because going through all the problems LanguageTool reported was much more boring than I expected, I wanted to give a subtle clue to my cause of death in case "dying from boredom" could really happen.

[SethFalco]

Looks like there's a conflict in pages/common/paci.md

Thanks for the heads-up, should be good to go!

[marchersimon]

Nice, I'll merge