Repository navigation
Fix typos in multiple blog posts - #159
Rafiaminhaj wants to merge 1 commit into
Conversation
- jit-on-track: misinterpertered -> misinterpreted - jit-on-track: affectionally -> affectionately - jit-on-track: overhwhelming -> overwhelming - meet-team-brett-cannon: spikein -> spike in - python-3100a4: releasee -> release - python-3100a2: releasee -> release - python-3100-is-available: propper -> proper - 2012-language-summit-report: fairlyquick -> fairly quick
I'm a little confused about this, can you explain more? |
|
I presume that's @willy-b ? |
|
Yes @StanFromIreland @hugovk , I hope it is not an issue to share typos with others looking for things to send PRs to fix! My goal is to help @Rafiaminhaj contribute as they asked to help in python/cpython#156233 (comment) . I replied there that I had already merged 1 PR and had another in review for that issue but could share new typos and other items that might need fixing. Thus, I looked around for typos (no AI or LLM) and last night sent these few blog typos and one possibly unintentional foreign word in the documentation (insecable instead of indivisible in the docs https://web.archive.org/web/20260912230722/https://docs.python.org/3.16/library/textwrap.html#textwrap.TextWrapper.break_on_hyphens#:~:text=insecable ) . I did warn I was unsure whether the team would take blog corrections as I haven't attempted to send fixes for those myself yet (I didn't have any other documentation typos on hand). Let me know if you have any objections or questions! |
|
I'm curious about how you look for typos, in this case, why not just use an LLM...? |
|
@StanFromIreland , great question. I find many of the typos and other issues manually reading (I also have successfully reported them and had them accepted in multiple print books, both typos and also conceptual mistakes) but I have also started using a Java program which I wrote that doesn't use any AI or LLMs to BFS webpages and look for typos, Python/Java syntax errors (maybe soon PHP). I don't use LLMs as tools for personal ethical reasons, documented on my life partner's webpage at https://github.com/i-am-ying-li#ethics (she is not helping me with typos or open source review). |
Summary
Fix multiple typos found across blog posts.
Changes
misinterperteredmisinterpretedaffectionallyaffectionatelyoverhwhelmingoverwhelmingspikeinspike inreleaseereleasereleaseereleasepropperproperfairlyquickfairly quickTypos identified by William Bruns (volunteer Python
community contributor).