diff --git a/duplicity-backup.conf.example b/duplicity-backup.conf.example
index b3af280..448a73e 100644
--- a/duplicity-backup.conf.example
+++ b/duplicity-backup.conf.example
@@ -50,17 +50,20 @@ ENCRYPTION='yes'
 
 # If you are NOT running this from a cron, comment this line out
 # and duplicity should prompt you for your password.
-# Otherwise this password is either used for symetric encryption
+# Otherwise this password is either used for symmetric encryption
 # (your backups will be encrypted with this password) or is used
 # for the "GPG_SIGN_KEY" (see below).
 # Comment out if you aren't using encryption
 PASSPHRASE="foobar_gpg_passphrase"
 
 # Specify which GPG keys you would like to use (even if you have only one).
-# It is highly recommended to create separate signature and encryption keys. 
-# When run, duplicity should prompt you for the GPG_SIGN_KEY password 
-# (or specify the PASSPHRASE above if you run this script from a cron).
-# Comment out if you're using only PASSPHRASE (symetric encryption) or not using 
+# If you are running this from a cron, it is highly recommended to create separate 
+# signature and encryption keys, because you have to specify the password for the 
+# GPG_SIGN_KEY via the above PASSPHRASE variable 
+# (see http://www.debian-administration.org/articles/209#d0e109).
+# If you are not running the script from a cron, duplicity should prompt you for the 
+# GPG_SIGN_KEY password.
+# Comment out if you're using only PASSPHRASE (symmetric encryption) or not using 
 # encryption at all.
 GPG_ENC_KEY="foobar_gpg_key"
 GPG_SIGN_KEY="foobar_gpg_key"