From a8e352acfd9e905127e08c3b7a0b3694c09a5e45 Mon Sep 17 00:00:00 2001
From: deajan <ozy@badministrateur.com>
Date: Sun, 16 Jun 2013 14:27:45 +0200
Subject: [PATCH] Update README.md

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 48acbec..a67fa1d 100644
--- a/README.md
+++ b/README.md
@@ -54,8 +54,8 @@ File backups can be done directly if data won't change while a backup is going o
 
 You may try your setup by specifying the "--dry" parameter which will run a simulation of what will be done.
 
-    $ ./obackup.sh path/to/config/file --dry
-    $ ./obackup.sh path/to/config/file
+    $ ./obackup.sh path/to/backup.conf --dry
+    $ ./obackup.sh path/to/backup.conf
 
 One you're happy with a test run, you may run obackup as a cron task with the "--silent" parameter so output will not be written to stdout.
 All backup activity is logged to "/var/log/obackup_backupname.log".