apply correct a / an rule

README.md

@@ -4,7 +4,7 @@ Book for rehabilitative coders.
 If you cannot code anymore because of a visual impairment, this book is for you.
 This book teaches the building blocks of a good coder without sight.
 
-Although this book is meant for people with an visual impairment, it can be interesting to read without an visual impairment.
+Although this book is meant for people with a visual impairment, it can be interesting to read without an visual impairment.
 Coding with eyes closed becomes less of a magic trick and more practical on how you can be a coder with a visual impairment.
 
 You can read the book on [codingwitheyesclosed.com](https://codingwitheyesclosed.com).

coding-with-eyes-closed/src/04-2-editor.md

@@ -38,7 +38,7 @@ Why? Because we only see 1 line at a time and it takes more time to understand w
 We want to be as productive as possible so we need to navigate to the right line as fast as possible.
 Language servers helps you do that.
 
-Lets say you have an error and no language server.
+Let's say you have an error and no language server.
 You have to read the error message of the compiler, which is most of the time in the terminal.
 Then you know the error, and you need to navigate to the right line in the right file. That costs time.
 

coding-with-eyes-closed/src/07-3-5-pr.md

@@ -5,7 +5,7 @@ Goal: Get familiar with reading code from someone else.
 ## Intro
 
 I really like open source software because I can make it accessible myself. 
-If an button is labelled bad for instance, I can change the label so that it has a better description.
+If a button is labelled bad for instance, I can change the label so that it has a better description.
 
 Reading someone elses code can be a challenge. Especially if that person is a bad coder. 
 Opening a pull request is an good way to train with reading code that you did not write.

coding-with-eyes-closed/src/09-0-cheat-sheet.md

@@ -44,7 +44,7 @@ You can see only a small portion of a script, so you should use the compiler as
 
 Dynamic types are blind. You are blind too. Dynamic types cannot lead you in the dark.
 Use static typed languages. Such as Java, Kotlin, Rust and many others.
-[5.2 Why dynamic types are even worse for some with an visual impairment](https://codingwitheyesclosed.com/05-2-dts.html)
+[5.2 Why dynamic types are even worse for some with a visual impairment](https://codingwitheyesclosed.com/05-2-dts.html)
 
 Use unit test as your sight. Write as many as possible. 
 This makes debugging relatively easy.

coding-with-eyes-closed/src/SUMMARY.md

@@ -12,7 +12,7 @@
   - [Navigating websites](04-3-websites.md)
 - [What language should I use?](05-0-language.md)
   - [The compiler is your sight](05-1-compiler.md)
-  - [Why dynamic types are even worse for someone with an visual impairment](05-2-dts.md)
+  - [Why dynamic types are even worse for someone with a visual impairment](05-2-dts.md)
   - [Why tests are so important for us](05-3-test.md)
   - [Make build pipelines that last](05-4-build-pipeline.md)
 - [Overcoming obstacles](06-0-obstacles.md)