diff --git a/README.md b/README.md
index 58b68fcf0..28abb2bbf 100755
--- a/README.md
+++ b/README.md
@@ -1,70 +1,85 @@
 # SETUP
 
- * These scripts were written and tested on Ubuntu 12.10 where bash is located at /bin/bash. You may need to create a symlink or edit these script accordingly.
+ * These scripts were written and tested on Ubuntu 12.10 where bash is located at /bin/bash. You may need to create a symlink or edit these scripts accordingly.
 
  * Please backup your database first. Something like this should do it.
 
     `mysqldump --opt -u root -p newznab > ~/newznab_backup.sql`
 
 
+
  * The first step is to decide whether or not you will convert your database to the InnoDB engine. The InnoDB has a lot of benefits, too many to list here, but more ram is required. How much exactly, depends on too many things to list here.
 
  * If you decide to convert your database, I recommend using [kevin123's github](https://github.com/kevinlekiller/Newznab-Barracuda.git). I recommend only converting the binaries a parts table, using compressed tables. But, there are many choices. I suggest you read his README and follow his recommendations. Or, simply:
 
-    `cd /var/www/newznab/misc/testing/`
+    `cd /var/www/newznab/misc/testing`
  
-    `git clone https://github.com/kevinlekiller/Newznab-InnoDB-Dropin.git innodb`
+    `git clone https://github.com/kevinlekiller/Newznab-InnoDB-Dropin.git kev-innodb`
 
-    `cd innodb/lib/innodb`
+    `cd kev-innodb/lib/innodb`
 
     `php convertToInnoDB.php`
 
 
- * If, you have already converted your database, and didn't to the steps above. You will need to clone [kevin123's github](https://github.com/kevinlekiller/Newznab-InnoDB-Dropin.git) and get the scripts.
+
+ * Now, you need to decide which branch you will use, the master branch uses scripts written by andrewit and the dev branch uses scripts written by kevin123. If, you choose the dev branch, skip the next step.
+
+ * If, you stay on the master branch, you will need to clone [andrewit's github](https://github.com/itandrew/Newznab-InnoDB-Dropin.git) and get his scripts.
 
     `cd /var/www/newznab/misc/testing/`
     
-    `git clone https://github.com/kevinlekiller/Newznab-InnoDB-Dropin.git innodb`
+    `git clone https://github.com/itandrew/Newznab-InnoDB-Dropin.git innodb`
     
 
- * Clone my github
+
+ * Now, Clone my github. Theses scripts should be able to run from any path, but this location is where I was asked to put it.
 
     `cd /var/www/newznab/misc/update_scripts/nix_scripts/`
     
     `git clone https://github.com/jonnyboy/newznab-tmux.git tmux`
     
-    -or-
-
-    `git clone https://github.com/kevinlekiller/newznab-tmux tmux`
-    
     `cd tmux`
     
+
+
+ * If, you choose the the dev branch, run:
+
+    `git checkout dev`
+
+
+
+ * Edit the paths, timers, username, what to run and then accept.
+
     `nano edit_these.sh`
 
 
- * Edit some permissions, run as root.
+
+ * Edit some permissions, run this as root. The file .tmux.conf will be copied to the users home folder. If, when you run ./start.sh you see 0 nzb's and you are sure there are more than 0 left to import, verify the path to the nzb's in .tmux.conf in the home folder of the user.
 
     `./set_perms.sh`
 
 
- * Run my script, as user.
+
+ * Run my script, as user. If, you have grsecurity in you kernel, you will need to run using sudo if you use nmon or bwm-ng.
 
     `./start.sh`
+
     
 
  * If you connect using **putty**, then under Window/Translation set Remote character set to UTF-8.
 
  * If something looks stalled, it probably isn't. If all 13 panes are still there, it is most likely, as it should be.
  
- * update_cleanup needs to be uncommented to actually do something, and update_parsing is good for fixing a few releases everytime it runs, not a silver bullet though
+ * You must edit **misc/testing/update_cleanup.php** in order for it to actually do something, and update_parsing is good for fixing a few releases everytime it runs, not a silver bullet though.
 
- * If you are running this on an OVH or kimsufi server, you may need to run sudo ./start.sh because they built grsecurity into the kernel.
-    
- * Now all panes should be running smoothly. If any of the scriptns in the top 3 panes crash, the panes should remain open and you should be able to view the error messages. I hope this helps.
+ * Now all panes should be running smoothly. If any pane crashes, it should remain open and return to the prompt. You should also be able to see the error that caused it to crash.
 
  * Join in the converstion at irc://moonlight.se.eu.synirc.net/newznab-tmux.
 
- * Thanks go to all who offered their assistance and improvement to these scripts.
+
+
+
+ * Thanks go to all who offered their assistance and improvement to these scripts, especially kevin123.
 
 <hr>
  * If, you find these scripts useful and would like to offer a donation, they are greatly appreciated. Thank you