diff --git a/Netgrimoire/Pocket/Deployment_Guide.md b/Netgrimoire/Pocket/Deployment_Guide.md
index a455129..d96cc4e 100644
--- a/Netgrimoire/Pocket/Deployment_Guide.md
+++ b/Netgrimoire/Pocket/Deployment_Guide.md
@@ -2,7 +2,7 @@
 title: Pocket Grimoire 
 description: 
 published: true
-date: 2026-02-21T16:33:03.912Z
+date: 2026-02-21T16:57:44.484Z
 tags: 
 editor: markdown
 dateCreated: 2026-02-20T04:41:35.122Z
@@ -706,12 +706,13 @@ zfs list vault/Green/Pocket
 # Create snapshot for initial send
 sudo zfs snapshot vault/Green/Pocket@initial
 
-# Send to pocket-green pool
-# Note: This sends the encrypted data, pocket-green will have its own encryption
+# Send to pocket-green pool, creating pocket-green/Pocket dataset
+# IMPORTANT: Must specify destination dataset name, not just pool name
 sudo zfs send vault/Green/Pocket@initial | \
-  sudo zfs receive pocket-green
+  sudo zfs receive pocket-green/Pocket
 
 # This creates: pocket-green/Pocket (matching the structure)
+# NOT just "pocket-green" (which is the pool name)
 
 # Verify received
 zfs list pocket-green/Pocket
@@ -737,6 +738,9 @@ du -sh /mnt/pocket-green/Pocket/
 - `pocket-green` pool has its own encryption (encrypts during receive)
 - Result: Data is encrypted at rest on both systems with different keys
 - The dataset name becomes `pocket-green/Pocket` (not `pocket-green/Green/Pocket`)
+- You MUST specify the full destination path including dataset name (`pocket-green/Pocket`)
+- Just specifying the pool name (`pocket-green`) will fail with "destination exists"
+
 
 
 **Populate MEDIA-FAMILY (optional - curate family content):**