chore: Spelling

[jsoref]

This PR corrects misspellings identified by the check-spelling action.

What is the previous behavior before this PR?

The misspellings have been reported at jsoref@55adbfb

What is the new behavior after this PR?

The action reports that the changes in this PR would make it happy: jsoref@dfc30bb

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.

[jsoref]

Most corrections automatically suggested by Google Sheets. All fault mine.

[jsoref]

This is a brand.

[jsoref]

Brand

[jsoref]

This item is consistently spelled this way, but the world disagrees...

https://www.merriam-webster.com/dictionary/vinculum

this is a TI(re)L - Google Sheets told me.

[ronkok]

Good stuff.

@edemaine I think you are the right person to decide if the variable name in macros.js should change from nonexistsOK to nonexistentOK. There might be some small nuance in play there.

All the rest looks good to me.

[edemaine]

Thanks @ronkok for reviewing! I agree that nonexistsOK would be better, for parallelism with existsOK. What we mean by nonexistsOK is "is it OK that the command doesn't exist?" Another possible spelling would be notExistsOK... is that better/clearer?

[codecov]

Codecov Report

Merging #3762 (e7c2d80) into main (c7b1f84) will not change coverage.
The diff coverage is 94.11%.

❗ Current head e7c2d80 differs from pull request most recent head ae36eab. Consider uploading reports for the commit ae36eab to get more accurate results

@@           Coverage Diff           @@
##             main    #3762   +/-   ##
=======================================
  Coverage   92.98%   92.98%           
=======================================
  Files          91       91           
  Lines        6770     6770           
  Branches     1574     1574           
=======================================
  Hits         6295     6295           
  Misses        437      437           
  Partials       38       38           

Impacted Files	Coverage Δ
contrib/render-a11y-string/render-a11y-string.js	83.80% <ø> (ø)
src/Parser.js	96.14% <ø> (ø)
src/buildMathML.js	97.67% <ø> (ø)
src/defineEnvironment.js	100.00% <ø> (ø)
src/environments/array.js	98.04% <ø> (ø)
src/fontMetrics.js	100.00% <ø> (ø)
src/functions/arrow.js	95.83% <ø> (ø)
src/functions/delimsizing.js	97.54% <ø> (ø)
src/mathMLTree.js	86.58% <ø> (ø)
src/parseNode.js	73.33% <ø> (ø)
... and 3 more

---

Continue to review full report in Codecov by Sentry.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update bd502a6...ae36eab. Read the comment docs.

[edemaine]

P.S. I think adding the "check spelling" action would be cool, as a separate PR, if there aren't any false positives (or there's an easy way to deal with them).

[jsoref]

Oops. Sorry (I failed to properly fill out the description -- fixed...). In regard to adding check-spelling..., you can see the configuration for check-spelling here: jsoref@55adbfb

functionally, https://github.com/jsoref/KaTeX/blob/55adbfb034441663fe62209bd9442cd750a7869b/.github/actions/spelling/expect.txt is a list of terms that check-spelling doesn't naturally recognize (with the addition of supplemental dictionaries) and that I didn't recognize as typos of anything else. You could think of them as "false-positives".

As for dealing w/ false-positives, I've been working on improving the flow. At this point, the current "easiest" approach can be seen in jsoref@55adbfb#commitcomment-94184527

To accept ✔️ these unrecognized words as correct and remove the previously acknowledged and now absent words, run the following commands

Basically the command will update the metadata and let you commit them. There's also a provision for updating metadata using a PR comment (which my company uses), but I don't have examples of it being generally deployed in public repositories.

I welcome feedback (it does take me some time to digest the feedback and implement a response, and this is a side project, but I try to be fairly responsive).

[edemaine]

Sorry for the delay on this. Feel free to submit a PR that adds this to the CI workflow; I imagine you'd be the expert on that.

[KaTeX-bot]

🎉 This PR is included in version 0.16.6 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀