Code analysis: spelling errors

[pkevan]

Many thousand mainly code comment level spellings exist within the repo, which is just untidy. Since the effort to change this is large, and it affects many files, unsure how to proceed aside from doing this piecemeal.

Is it worth the effort, or should it just be tackled adhoc?

[pkevan]

further analysis reveals that a lot of these are through the translation files, so not quite as big an issue as initially thought.

[kraftbj]

I think piecemeal is fine. I can be sure to merge those quickly so nothing grows stale.

[priethor]

Could we consider this Documentation or Code quality rather than a bugfix? From experience in core and Gutenberg, anything that doesn't fix something for the user or extender shouldn't be considered a bugfix.

[kraftbj]

I'm good with that. I didn't see an option in GH for a custom issue types, but can go back to old fashioned labels.

[pkevan]

Since the initial PRs have been merged, I think we're good to close this issue as resolved.