diff --git a/ZFS-RAIDs.md b/ZFS-RAIDs.md
index 26879ba6aea1863d967ddbd6a889f507e871dc96..6cab67bf0e21970138bcb7ed0342d6f02036d076 100644
--- a/ZFS-RAIDs.md
+++ b/ZFS-RAIDs.md
@@ -1,14 +1,14 @@
 # ROADMAP
 - [x] RAID{0,1,6,10}
 - [x] ZFS description and capabilities
-- [ ] RAID implementations in ZFS
+- [X] RAID implementations in ZFS
 - [ ] Cache systems in ZFS
 ___
 
 - [ ] ZFS for DB or lvm+ext4
 
 # RAIDs
-**R**edundant **A**rray of **I**ndependent **D**isks
+### **R**edundant **A**rray of **I**ndependent **D**isks
 
 ## Some recorrent terms when defining a RAID system:
 **PARITY** 
@@ -56,7 +56,7 @@ ___
 
 
 # ZFS
-**Z**ettabyte **F**ile **S**ystem
+### **Z**ettabyte **F**ile **S**ystem
 
 Usually, data management involves physical and logical aspects. The first being the raw HardDrives and SDs organized in blocks and the second being the logical block devices as seen by the operation system. The logical part can use multiple layers as volume managers and RAID controllers.
 
@@ -66,4 +66,9 @@ As described in the documentation, one of the most powerful capabilities of ZFS
 
 With the snapshot option, it's also possible to replicate a entire and independet file system. And it's implementation lets several numbers of snapshots to be taken without losing performance.
 
+## RAIDs with ZFS
+ZFS implements versions of RAID0, RAID1 and RAID6. The first and second one are called as their most known names: RAID0 and RAID1. For parity-type RAIDS as RAID5 and RAID6, ZFS calls them as RAIDZ-{1,2,3}, the number being the total amount of parity disks available in the physical blocks.
 
+As known in RAID10 implementation, ZFS can take two or more RAID1 tank arrangements to make a RAID0 array, resulting in a RAID10 setup. This setup needs at least four total disks
+
+It's important to know that a RAID0 and RAID1 requires at least two disks, and any RAID-Z requires at least n+2 disks, n being the total amount of parity disks available in the system.