diff --git a/RAID0.png b/RAID0.png
new file mode 100644
index 0000000000000000000000000000000000000000..3a0086ae7d39f77694898d6d964987b1fc3f7a6a
Binary files /dev/null and b/RAID0.png differ
diff --git a/ZFS-RAIDs.md b/ZFS-RAIDs.md
index 5746ee50af3ca648afff02f15bd00d1a38036b8c..e796e2032e7ef99a31e900358bed81861371e761 100644
--- a/ZFS-RAIDs.md
+++ b/ZFS-RAIDs.md
@@ -1,15 +1,16 @@
-#Usefull RAIDs with ZFS
-**R**edundant
-**A**rray of
-**I**ndependent
-**D**isks
+# Usefull RAIDs with ZFS
+**R**edundant **A**rray of **I**ndependent **D**isks
 
-##Some recorrent terms when defining a RAID system:
+## Some recorrent terms when defining a RAID system:
 **PARITY:** 
 :   Refers to  ==parity bit==, it's a bit added to a string that says if the sum of bits in the string is even/odd, it's a simple form of error checking. Commonly the parity bit is added in the end of each byte (8 bits).
 
     
-##RAID0
+## RAID0
+    ![RAID0 diagram](RAID0.png)
+
     RAID0 splits data across a multiple-disks array. The ideal setup is equaly-sized disks since the total storage used in a RAID0 arrangement is equal to the lower storage disk space times the total amount of disks. I a array of one 120Gb disk and one 360Gb disk, the total storage available would be 240 Gb.
     RAID0 create stripes of data so disk operations are n-times faster, n being the total amount of disks available. It also distributes I/O costs between all disks making it a very fast storage system. RAID0 **doesn't implements parity** or even any **fault tolerance**, so the failure of one single disk in the array will result in total data loss. 
     Besides fastness, RAID0 also is a good system to create large amounts of data storage units with lesser disks, since all disks in the array have unique information and, having equaly-sized units, uses 100% it's fisical capability as storage.
+
+## RAID1