Typos

Author: rexim

README.md

@@ -8,9 +8,9 @@ Custom coroutines implementation in GNU C.
 
 Coroutine is a lightweight user space thread with its own stack that can suspend its execution and switch to another coroutine on demand. Coroutines do not run in parallel but rather cooperatively switch between each other whenever they feel like it.
 
-Coroutines are useful in cases when all your program does majority of the time is waiting on IO. So with coroutines you have an opportunity to switch the context and go do something else. It is not useful to split up heavy CPU computations because they all going to be executed on a single thread. Use proper thread for that (pthreads on POSIX).
+Coroutines are useful in cases when all your program does majority of the time is waiting on IO. So with coroutines you have an opportunity to switch the context and go do something else. It is not useful to split up heavy CPU computations because they all going to be executed on a single thread. Use proper threads for that (pthreads on POSIX).
 
-Good uses case for coroutines are usually Network Applications and UI. Anything with a slow Async IO.
+Good use cases for coroutines are usually Network Applications and UI. Anything with a slow Async IO.
 
 <!-- End of the copy of the section -->
 

coroutine.h

@@ -12,9 +12,9 @@
 // time is waiting on IO. So with coroutines you have an opportunity to do
 // coroutine_yield() and go do something else. It is not useful to split up
 // heavy CPU computations because they all going to be executed on a single
-// thread. Use proper thread for that (pthreads on POSIX).
+// thread. Use proper threads for that (pthreads on POSIX).
 //
-// Good uses case for coroutines are usually Network Applications and UI.
+// Good use cases for coroutines are usually Network Applications and UI.
 // Anything with a slow Async IO.
 //
 // # How does it work?