From fed0640f5ce59ac8c9f0cae7f5484c2574141349 Mon Sep 17 00:00:00 2001 From: Michael Stanclift Date: Fri, 12 Feb 2021 10:38:50 -0600 Subject: [PATCH] Updated System Requirements (markdown) --- System-Requirements.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/System-Requirements.md b/System-Requirements.md index 59016a4..92d28e0 100644 --- a/System-Requirements.md +++ b/System-Requirements.md @@ -49,6 +49,6 @@ You will need to designate one Pi-Hole as primary and at least one as secondary. - The primary Pi-hole is where you'll make most of your configuration changes through the Web UI, doing things such as; manual allow-listing, adding block-lists, device/group management, configuring custom/local network DNS, and changing other list settings. - The secondary Pi-hole(s) are where you will install and configure Gravity Sync. -The primary Pi-hole will also be referred to in the interface as remote, while the secondary will be referred to as local. This is done to be as confusing as possible and make sure you read the documentation. (Just kidding) +The primary Pi-hole will also be referred to in the interface as remote, while the secondary will be referred to as local. This is done to be as confusing as possible and make sure you read the documentation. (Just kidding) The default operation is to pull data from the primary to the secondary, and to put the operational load of Gravity Sync on what is expected to be a less active Pi-hole device. See also: [Reference Architectures](https://github.com/vmstan/gravity-sync/wiki/Reference-Architectures) \ No newline at end of file