From cbf8046ad2693fd2fc9df2862bad52c0b362096e Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Wed, 13 Apr 2022 10:02:28 -0500 Subject: [PATCH] Updated Engaging (markdown) --- Engaging.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Engaging.md b/Engaging.md index e122eab..4d6fb40 100644 --- a/Engaging.md +++ b/Engaging.md @@ -2,7 +2,7 @@ Before you Engage in your first sync, make sure that you have [installed and con ## Dry Run -You can run a comparison between remote and local databases, which will be non-disruptive, and see if everything has been configured correctly. +Run a comparison between remote and local databases, which will be non-disruptive, and see if everything has been configured correctly. Do this from both Pi-hole. ```bash gravity-sync compare @@ -12,7 +12,7 @@ Assuming Gravity Sync runs successfully, it will indicate if there are changes p ## First Sync -You must now pick the Pi-hole instance that currently has the "authoritative" list of settings and run the following command to send all of those settings to its peer for the first time. +You must now pick the Pi-hole instance that currently has the "authoritative" list of settings and run the following command to send all of those settings to its peer for the first time. Do this only from the authoritative Pi-hole. ```bash gravity-sync push