New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Typos in Numba Documentation #9234
Comments
@SridharCR thank you for raising this! How many typos are we talking here an what would be scope of your proposed PR? Also, what would you suggest to use to prevent such typos in the future? |
@esc In docs folder, there are approximately 76 typos are listed down. I'm thinking of integrating the codespell to the project's precommit or github workflow to prevent the typos in the future. It also helps in listing the issues and fixing these typos with utils, instead of manual fixes. Share your comments on the same... |
@SridharCR thank you for pointing us in this direction and thank you for your efforts to improve Numba. I tried codespell just now and will summarize my findings here: I ran the following (all in directory
So this suggests that there are 75 typos. The are:
Looking closer at this list, there are several duplicates and false positives. For example "Collison" is a name and "HSA" is a real term: https://en.wikipedia.org/wiki/Heterogeneous_System_Architecture Following this, I crafted an ignore file as such:
Running this again yields:
Which reduces the total number of typos by almost 2/3. Looking closer at the results themselves:
Many of the typos are in the release notes, which are a snapshot of what happened. I don't think those are too bad. Discounting the stuff in release-notes and also the re-use vs reuse (stylistic choice IMHO), leaves us:
I think these 7 are legitimate typos that you could make a PR for, that would be fine. It's less than 10% of what codespell reported by default, but still nice finds! 🙌 About the Github action or other automation: given the large number of false positives, I am not convinced that this could be automated very well and I would like to keep a human in the loop to be on the safe side. So, instead I think it will be best for the release manager (RM) to run codespell manually on the docs before a release to catch anything that was missed during review. This is a 5-10 minute task once every release so I think that is feasible. Moving forward on this idea, an additional bullet would be added to the release checklists to make sure |
@SridharCR thank you again for pointing out codespell, I went and used it on the llvmlite project too and found two typos there: ❤️ |
Cool @esc, then I can fix the typos for now, and we can skip the automated spell checks. |
Typos in Numba Documentation
visible in the change log (https://github.com/numba/numba/blob/main/CHANGE_LOG).
i.e. it's possible to run as 'python bug.py'.
There are multiple typos with Numba documentation such as, I have listed down few of them.
.\source\user\installing.rst:8: compatability ==> compatibility (https://numba.readthedocs.io/en/stable/user/installing.html#compatibility)
.\source\user\parallel.rst:133: noticable ==> noticeable
(https://numba.readthedocs.io/en/stable/user/parallel.html#explicit-parallel-loops)
.\source\proposals\jit-classes.rst:198: inhertance ==> inheritance
(https://numba.readthedocs.io/en/stable/proposals/jit-classes.html#inheritance)
etc.
Happy to fix all the typos and add some tests to prevent typos in the future.
The text was updated successfully, but these errors were encountered: