From c1d828bb176b12336a98aa659403fbf630bd23de Mon Sep 17 00:00:00 2001 From: Connor Kennedy Date: Wed, 29 Jan 2020 14:22:11 -0600 Subject: [PATCH] Update README.md --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index e569613..8246da0 100644 --- a/README.md +++ b/README.md @@ -145,7 +145,7 @@ to enter and save your credentials. Now you can run `pihole-cloudsync` unattende Again, **the above steps must be performed on each Pi-hole you wish to use with `pihole-cloudsync`.** # Automation -There are two options for automating unattended runs pihole-cloudsync, [cron](#Automating-with-cron) and [systemd](#Automating-with-systemd). See below for details or use the links to skip right to your desired section +There are two options for automating unattended runs of pihole-cloudsync, [cron](#Automating-with-cron) and [systemd](#Automating-with-systemd). See below for details or use the links to skip right to your desired section ## Automating with cron Once each Pi-hole's local Git repo has been configured to save your login credentials, you can automate your Primary Pi-hole's "push" and your Secondary Pi-holes' "pull" in any number of ways. The simplest way is to run a simple cron job a few times a day.