updated READMEs

README.md

@@ -38,19 +38,21 @@ How to use this tutorial
 you jump right to folder 05 and don't know why there is a `mov ah, 0x0e`, it's because you missed lecture 02.
 Really, just go in order. You can always skip stuff you already know.
 
-2. Read each README first. Especially the first line, which details the concepts you should be familiar with
-before reading the code.
+2. Open the README and read the first line, which details the concepts you should be familiar with
+before reading the code. Google concepts you are not familiar with. The second line states the goals for each lesson. 
+Read them, because they explain why we do what we do. The "why" is as important as the "how".
+ 
+3. Read the rest of the README. It is **very concise**.
 
-3. Read the README. It is **very concise**. The only theory is the required to understand the code and there
-are tips on what to look at when you open the code file(s)
+4. (Optional) Try to write the code files by yourself after reading the README.
 
-4. Look at the code examples. Some times you may be able to write them yourself just from the hints on the README.
+5. Look at the code examples. They are extremely well commented.
 
-5. Experiment with them and try to break things. Try to change pointers and registers and see what happens. You know, the usual.
+6. (Optional) Experiment with them and try to break things. The only way to make sure you understood something is
+trying to break it or replicate it with different commands.
 
 
-TL;DR: First read the README on each folder, then decide if you will
-implement it yourself or just read the provided code files.
+TL;DR: First read the README on each folder, then the code files. If you're brave, try to code them yourself.
 
 
 Contributing