diff --git a/Debian-Stretch-Root-on-ZFS.md b/Debian-Stretch-Root-on-ZFS.md
index 9308d55..155755f 100644
--- a/Debian-Stretch-Root-on-ZFS.md
+++ b/Debian-Stretch-Root-on-ZFS.md
@@ -145,6 +145,12 @@ The primary goal of this dataset layout is to separate the OS from user data. Th
     # zfs create -o com.sun:auto-snapshot=false \
                  -o mountpoint=/var/lib/nfs      rpool/var/nfs
 
+    If this system will use Snap packages:
+    # zfs create                                 rpool/var/snap
+
+    If you use /var/www on this system:
+    # zfs create                                 rpool/var/www
+
     If you want a separate /tmp dataset (choose this now or tmpfs later):
     # zfs create -o com.sun:auto-snapshot=false  rpool/tmp
     # chmod 1777 /mnt/tmp
diff --git a/Ubuntu-18.04-Root-on-ZFS.md b/Ubuntu-18.04-Root-on-ZFS.md
index db1d8c2..e81ae2f 100644
--- a/Ubuntu-18.04-Root-on-ZFS.md
+++ b/Ubuntu-18.04-Root-on-ZFS.md
@@ -169,6 +169,12 @@ With ZFS, it is not normally necessary to use a mount command (either `mount` or
     # zfs create -o com.sun:auto-snapshot=false \
                  -o mountpoint=/var/lib/nfs      rpool/var/nfs
 
+    If this system will use Snap packages:
+    # zfs create                                 rpool/var/snap
+
+    If you use /var/www on this system:
+    # zfs create                                 rpool/var/www
+
     If you want a separate /tmp dataset (choose this now or tmpfs later):
     # zfs create -o com.sun:auto-snapshot=false  rpool/tmp
     # chmod 1777 /mnt/tmp