Update README.md

Author: brunoborges

Diff for: README.md

@@ -16,20 +16,20 @@ Prerequisites
 
  - linux.git: You will need our branch with the AFL patches and satconfig patches:
 
-    $ git pull https://github.com/vegard/linux-2.6.git v4.6+kconfig-sat
+        $ git pull https://github.com/vegard/linux-2.6.git v4.6+kconfig-sat
 
  - kvm/qemu: KVM is required for certain fuzzers or if you just want to use KVM instead of UML.
 
  - gcc 5: gcc 5 or later is needed for building the kernel using our instrumentation plugin. On Ubuntu you can do:
 
-    $ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
-    $ sudo apt-get update
-    $ sudo apt-get install gcc-5
+        $ sudo add-apt-repository ppa:ubuntu-toolchain-r/test
+        $ sudo apt-get update
+        $ sudo apt-get install gcc-5
 
  - Python packages: jinja2 and yaml. On Ubuntu you can do:
 
-    $ sudo apt-get install python-jinja2
-    $ sudo apt-get install python-yaml
+        $ sudo apt-get install python-jinja2
+        $ sudo apt-get install python-yaml
 
 
 Prepare the kernel branch
@@ -41,7 +41,7 @@ Prepare the kernel branch
 
 3. Merge the satconfig branch:
 
-    $ git pull https://github.com/vegard/linux-2.6.git v4.6+kconfig-sat
+        $ git pull https://github.com/vegard/linux-2.6.git v4.6+kconfig-sat
 
 4. Set the 'linux_afl_rev' variable in config.yml to point to the resulting commit (can be a branch, a sha1, or even just 'HEAD')
 
@@ -59,26 +59,26 @@ Launch a fuzzer
 
 2. Run the following command:
 
-    $ bin/start --master ext4 0
+        $ bin/start --master ext4 0
 
 This should start a single ext4 fuzzer in the current screen window.
 
 3. If the fuzzer stops or crashes, you can resume it later with:
 
-    $ bin/start --resume --master ext4 0
+        $ bin/start --resume --master ext4 0
 
 4. If you want to start additional fuzzers, create a new screen window and run e.g.:
 
-    $ bin/start ext4 1
+        $ bin/start ext4 1
 
 5. If you want to run many fuzzers in parallel, it is advised that you bind each fuzzer to a single, specific CPU:
 
-    $ taskset -c 0 bin/start --master ext4 0
-    $ taskset -c 1 bin/start ext4 1
-    ...
+        $ taskset -c 0 bin/start --master ext4 0
+        $ taskset -c 1 bin/start ext4 1
+        ...
 
 
 How to contribute
 =================
 
-Please see CONTRIBUTING.md.
+Please see [CONTRIBUTING](./CONTRIBUTING.md).