Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
Disclaimer: GitHub does not like PRs w/ >250 commits (this has 465 at the time of filing). In general, reviewing windowed views is probably better than most alternatives (the standard git cli's diff output is fairly unhelpful for PRs like this).
Note: I fully expect to be asked to split this PR / reorganize it. If there are files that shouldn't be changed, let me know, dropping files is easy. If there are terms that can't be changed, that's also easy -- right now, a term is localized to a single commit, so dropping it means just dropping the commit.
It's possible for me to split by kind of content (comment vs code), but such things are moderately expensive and I try to do it as few times as possible and as late as possible.
I'll try to include annotations about the changes, but it'll take me a bit (it's a long PR)
This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/omi/commit/9ac24b5d4b6dfdecf096517ad6ddc5fc88424ec3#commitcomment-57009226
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/omi/commit/4bed8cacc5b045d30cc70fa953c12a89c96dbaab
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.
Disclaimer: GitHub does not like PRs w/ >250 commits (this has 465 at the time of filing). In general, reviewing windowed views is probably better than most alternatives (the standard git cli's diff output is fairly unhelpful for PRs like this).
Note: I fully expect to be asked to split this PR / reorganize it. If there are files that shouldn't be changed, let me know, dropping files is easy. If there are terms that can't be changed, that's also easy -- right now, a term is localized to a single commit, so dropping it means just dropping the commit.
It's possible for me to split by kind of content (comment vs code), but such things are moderately expensive and I try to do it as few times as possible and as late as possible.
I'll try to include annotations about the changes, but it'll take me a bit (it's a long PR)