diff --git a/compare.html b/compare.html
index 627adac6..58ac558d 100644
--- a/compare.html
+++ b/compare.html
@@ -180,6 +180,7 @@ http://www.eecs.berkeley.edu/Pubs/TechRpts/1987/5853.html
 
 <p>
 <a id="note1">[1]</a> - unRAID lacks native checksums and ignores silent errors. If a parity error results from a silent data error, the parity is automatically recomputed, making it impossible to recover the silent error, even manually.
+To get a similar functionality of SnapRAID, you have to use the Btrfs filesystems for all your data disks.
 </p>
 
 <p>
@@ -207,7 +208,10 @@ ZFS also employs a suboptimal RAID-Z3 algorithm that requires roughly twice the
 </p>
 
 <p>
-<a id="note8">[8]</a> - unRAID can use integrity checksums via plugins like <a href="https://forums.lime-technology.com/topic/43290-dynamix-file-integrity-plugin/">Dynamix File Integrity</a>, <a href="https://forums.lime-technology.com/topic/41708-checksum-suite/">Checksum Suite</a>, or <a href="https://forums.lime-technology.com/topic/35615-bunker-yet-another-utility-for-file-integrity-checks/">bunker</a>. However, these are independent of parity processing and not used to aid recovery. For example, when recovering a single failed disk with dual parity, checksums can identify additional silent errors to facilitate recovery.
+<a id="note8">[8]</a> - unRAID can use integrity checksums via plugins like <a href="https://forums.lime-technology.com/topic/43290-dynamix-file-integrity-plugin/">Dynamix File Integrity</a>, or <a href="https://forums.lime-technology.com/topic/35615-bunker-yet-another-utility-for-file-integrity-checks/">bunker</a>.
+However, these are independent of parity processing and not used to aid recovery.
+For example, when recovering a single failed disk with dual parity, checksums can identify additional silent errors to facilitate recovery.
+To get a similar functionality of SnapRAID, you have to use the Btrfs filesystems for all your data disks.
 </p>
 
 <p>