diff --git a/content/2.md b/content/2.md
index bdc8841..a956eee 100644
--- a/content/2.md
+++ b/content/2.md
@@ -11,10 +11,11 @@ RAID protects you against one and only one thing: a disk failure. It does **not*
 
 * Multiple disk failures beyond the RAID level chosen (e.g. both disks in a mirror, or 3 disks in a RAID-6).
 * Failure of the RAID controller itself (especially when using hardware RAID), the computer itself, or the environment (a flood, or fire, perhaps).
-* Data corruption on-disk (except for ZFS, and especially for BTRFS) from cosmic rays, or minor hardware or firmware failures.
-* File corruption from bad writes or bit rot (except for ZFS), including whole-volume corruption from administrative mistakes (e.g. `mkfs` on an existing filesystem).
-* Malicious or accidental deletion or modification of data by yourself or another party, including viruses.
+* Data corruption on-disk from filesystem bugs, cosmic rays, or minor hardware or firmware failures.
+* Malicious or accidental deletion or modification of files by yourself or another party, including viruses, bad application writes, or administrative mistakes (e.g. `mkfs` on an existing filesystem).
 
 The adage is simple: "RAID replicates **everything**, even the stuff you don't want, like the deletion of that file you needed."
 
 For these reasons and more, RAID IS NOT A BACKUP!
+
+ZFS is an interesting case: while it does protect from corruption, it is still susceptable to the other failure modes and hence is still NOT A BACKUP!