diff --git a/Execution.md b/Engaging.md
similarity index 83%
rename from Execution.md
rename to Engaging.md
index 89746f3..73dc108 100644
--- a/Execution.md
+++ b/Engaging.md
@@ -1,6 +1,8 @@
-## Execution
+Before you Engage in your first sync, make sure that you have [installed and configured](https://github.com/vmstan/gravity-sync/wiki/Installation) Gravity Sync on both of your Pi-hole.
 
-Now, test Gravity Sync. You can run a comparison between remote and local databases, which will be non-disruptive, and see if everything has been configured correctly.
+## 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.
 
 ```bash
 gravity-sync compare
@@ -8,6 +10,8 @@ gravity-sync compare
 
 Assuming Gravity Sync runs successfully, it will indicate if there are changes pending between the two databases.
 
+### 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.
 
 ```bash
@@ -16,7 +20,7 @@ gravity-sync push
 
 If you do not follow this step, especially if one of your Pi-hole instances is a fresh install, you run the risk of overwriting your current configuration with a default setup or something else less desireable.
 
-### The Sync
+### Standard Orbit
 
 The default command for Gravity Sync is simple.