Minor typo in repository About description

[pixelatedkisses]

Just wanted to point out a quick typo in the repository's main "About" section on the right-hand sidebar.

"An Alternative library for uvloop compatability with windows" should be spelled "compatibility".

Since this is in the repo description settings, I couldn't open a PR to fix it for you.

[evnchn]

Some more for ya:

• README.md:275 — “apperciated” → appreciated (Contributing section)
• winloop/includes/compat.h:176 — “incase” → in case, and “accidently” → accidentally (same comment line)
• winloop/handles/process.pyx:503 — “libary” → library (comment)
• tests/test_base.py:583 — “invovles” → involves (comment)
• tests/test_aiomultiprocess.py:25 — “releated” → related (skip-reason string)

[Vizonex]

@evnchn @pixelatedkisses Would it help if I added a autocorrect system or workflow (ex: pre-commit) to try and aid this problem?

[evnchn]

It would

In fact I got you that list after screening codespell flagged entries

Feel free to copy a working codespell config from NiceGUI repo. But you would need to manage the exclusions of false positives

[pixelatedkisses]

Yes. I would suggest using an IDE extension to catch errors before pushing to Github, although it requires a bit of setup.

[Vizonex]

@evnchn @pixelatedkisses The soonest I can work on a fix is tomorrow to around a week due to my Job schedule outside of here. The workflow change is what adds a bit of wait time to this. I have removed the unplanned label as there is now a plan on how to fix this.

[evnchn]

#146 helps you by making the diff smaller when you want to add pre-commit

[Vizonex]

#146 helps you by making the diff smaller when you want to add pre-commit

I might not get to pre-commit now that I think about it but I did merge your PR the thing is that I am planning to decommission winloop and move it straight into the uvloop project where I will help maintain uvloop when everything is said and done. MagicStack/uvloop#736 Currently I am looking for extra volunteers to help with this effort so that a lot of costly maintenance with both projects can ultimately be saved. I'll probably look into making an actual issue about it soon depending on how much work is actually put in.