From 33632c04b6e91232fa33d083271d1f229b4c4fcd Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Mon, 1 Jun 2020 21:05:05 -0500 Subject: [PATCH] Cleaning --- README.md | 1 - 1 file changed, 1 deletion(-) diff --git a/README.md b/README.md index d7731e8..defa437 100644 --- a/README.md +++ b/README.md @@ -62,7 +62,6 @@ Now, test Gravity Sync. You can run a comparison between primary and secondary d 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 whitelist/blacklist on your primary Pi-hole, such as changing a description field or disabling a whitelist item, and then running `./gravity-sync.sh compare` again to validate your installation is working correctly. ### The Pull Function - The Gravity Sync Pull, is the standard method of sync operation, and will not prompt for user input after execution. It will perform some checks to help insure success and then stop before making changes if it detects an issue. It will also perform the same `compare` function outlined above, and if there are no changes pending, it will exit without making an attempt to copy data. ```bash