Diff
1diff --git a/duplicity-backup.conf.example b/duplicity-backup.conf.example
2index cb09289031d1902ba0a2657950828a68df49fc7d..a8da54c6ac722147b558cd18095185ec5cf9fbc4 100644
3--- a/duplicity-backup.conf.example
4+++ b/duplicity-backup.conf.example
5@@ -39,12 +39,12 @@
6 # !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
7
8 # AMAZON S3 INFORMATION
9-# Comment out this lines if you're not using Amazon S3
10+# Comment out these lines if you're not using Amazon S3
11 AWS_ACCESS_KEY_ID="foobar_aws_key_id"
12 AWS_SECRET_ACCESS_KEY="foobar_aws_access_key"
13
14 # S3CMD INFORMATION
15-# Most people don't need that, but in some cases
16+# Most people don't need this, but in some cases
17 # you may want to specify a custom configuration file
18 # to pass to s3cmd. If so, set the S3CMD_CONF_FILE variable
19 # to the full path of this custom config file.
20@@ -139,7 +139,7 @@ STATIC_OPTIONS="--full-if-older-than 14D --s3-use-new-style"
21 # Because duplicity will continue to add to each backup as you go,
22 # it will eventually create a very large set of files. Also, incremental
23 # backups leave room for problems in the chain, so doing a "full"
24-# backup every so often isn't not a bad idea.
25+# backup every so often is not a bad idea.
26 #
27 # You can either remove older than a specific time period:
28 #CLEAN_UP_TYPE="remove-older-than"