From a27743bd320bd4a370d921acc0be51acf1d7d651 Mon Sep 17 00:00:00 2001
From: jsloane <186535+jsloane@users.noreply.github.com>
Date: Sat, 17 Jun 2023 16:30:48 +1000
Subject: [PATCH] Update README.md (#230)

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 060c617..df226ac 100644
--- a/README.md
+++ b/README.md
@@ -928,7 +928,7 @@ BACKUP_SOURCES=/backup/app2_data
 
 If you want to manage backup retention on different schedules, the most straight forward approach is to define a dedicated configuration for retention rule using a different prefix in the `BACKUP_FILENAME` parameter and then run them on different cron schedules.
 
-For example, if you wanted to keep daily backups for 7 days, weekly backups for a month, and retain monthly backups forever, you could create three configuration files and mount them into `/etc/dockervolumebackup.d`:
+For example, if you wanted to keep daily backups for 7 days, weekly backups for a month, and retain monthly backups forever, you could create three configuration files and mount them into `/etc/dockervolumebackup/conf.d`:
 
 ```ini
 # 01daily.conf