diff --git a/Common-snapshots-and-holds.md b/Common-snapshots-and-holds.md
index f41e63e..5661849 100644
--- a/Common-snapshots-and-holds.md
+++ b/Common-snapshots-and-holds.md
@@ -20,9 +20,11 @@ There are a few rules for ZFS however:
 
 ## Holds to the rescue
 
-To prevent accidental deletion of the common snapshot zfs-autobackup uses holds.
+To prevent accidental deletion of the common snapshot we use "holds". A snapshot that is held cannot be destroyed, until its released with `zfs release`. (Use `zfs holds` to see the holds for a specific snapshot)
 
-This can be quite frustrating for new users who try to delete old datasets that still have holds. (`Dataset is busy`) Use `zfs holds ` and `zfs release` to release a snapshot.
+zfs-autobackup will automatically hold the common snapshot on both sides. It will automatically release them as soon as there is a newer common snapshot. 
+
+This can be quite frustrating for new users who try to delete old datasets that still have holds. (`Dataset is busy`) So you might be tempted to use `--no-holds`. Usually this is fine, but keep on reading.
 
 ## Holds and offline backups
 
@@ -38,10 +40,5 @@ Now holds are very important: In snapshot-only mode it looks at the holds to see
 
 
 
- 
-
-
-
-