diff --git a/Installing.md b/Installing.md
index 61f18fa..3d14a9f 100644
--- a/Installing.md
+++ b/Installing.md
@@ -45,7 +45,11 @@ Now, test Gravity Sync. You can run a comparison between primary and secondary d
 ./gravity-sync.sh compare
 ```
 
-Assuming Gravity Sync runs successfully, it will indicate if there are changes pending between the two databases. If not, make a subtle change to a allow/block list on your primary Pi-hole, such as changing a description field or disabling a allow list item, and then running `./gravity-sync.sh compare` again to validate your installation is working correctly.
+Assuming Gravity Sync runs successfully, it will indicate if there are changes pending between the two databases. 
+
+**Important!** If you have just performed a fresh install of your secondary Pi-hole (where Gravity Sync is now installed) and it's list configurations do not already match your primary, make a subtle change to a allow/block list on your _primary_ Pi-hole (such as changing a description field or disabling a allow list item) before running your first sync.
+
+Failure to do so may overwrite your primary configuration with the secondary's default/generic Pi-hole configuration.
 
 ### The Sync