fix spelling in docs, code comments, strings & non-exported names

[cr7pt0gr4ph7]

Fixed all spelling issues that I could find (using an automated spell checker to find the issues, resolution was always chosen manually). I have explicitly excluded exported names/functions from this PR (even those that are only intended for use within Vike itself) to avoid any possible breakages, those can currently be found in the cr7pt0gr4ph7/vike:fix-spelling-public branch and will follow in a second PR.

[brillout]

Very nice! Although, to avoid merge conflicts, let's revert the typo fixes in the source code (i.e. inside the vike/ directory).

[brillout]

FYI #1943.

using an automated spell checker

Which one did you use? CC @IanWorley

[brillout]

I went ahead and applied the changes and merged. Thank you! Contribution welcome to #1943.

[IanWorley]

FYI #1943.

using an automated spell checker

Which one did you use? CC @IanWorley

As of right now I went ahead and decide to use typos-rs-npm @brillout

[cr7pt0gr4ph7]

Very nice! Although, to avoid merge conflicts, let's revert the typo fixes in the source code (i.e. inside the vike/ directory).

These were the main goal of this PR, also fixing up the docs was just an add-on 😅 (Cause they were annoying me while debugging something...). Any chance to get at least the spelling fixes for comments & user-facing strings in?

[cr7pt0gr4ph7]

All merge conflicts should be easily fixable though, because there are no renames that affect multiple files at once in this PR, only local renames.

(And if it is decided to a spell checker in CI, most/all of these would have to be fixed anyway at some point - so better fix them now IMO).

[brillout]

We plan to merge all pending work, so that we'll have 0 pending PRs and 0 pending branches. We'll then be able to do it.

But it's going to take a little while as we're currently focusing on a couple of higher priorities. Very much looking forward to get Vike's backlog completely done.

The merge conflicts are really annoying, so I'm fairly convinced it's worth it to postpone it.

That said, you can still effectively contribute by contributing to the upcoming spellcheck CI, if you're up for it.

(And if it is decided to a spell checker in CI, most/all of these would have to be fixed anyway at some point - so better fix them now IMO).

The CI will only apply to docs/ for now.