summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2014-06-25 21:43:18 +0100
committerLars Wirzenius <liw@liw.fi>2014-06-25 21:43:18 +0100
commite46ecfacf9278510ec00fa9d9c68089d6621284c (patch)
treeb34ae88316c95b0556b678aaf1cd91b210bfc2f1
parent58bfac863fea033187a63eabd7ea8cea048adcc1 (diff)
downloadobnam-e46ecfacf9278510ec00fa9d9c68089d6621284c.tar.gz
Remove duplicate the
-rw-r--r--manual/en/060-backing-up.mdwn2
-rw-r--r--obnam.1.in2
2 files changed, 2 insertions, 2 deletions
diff --git a/manual/en/060-backing-up.mdwn b/manual/en/060-backing-up.mdwn
index 6d9e7dbf..56169cc9 100644
--- a/manual/en/060-backing-up.mdwn
+++ b/manual/en/060-backing-up.mdwn
@@ -233,7 +233,7 @@ De-duplication in Obnam is useful in several situations:
are unmodified, only the new data needs to be backed up.
* When a file or directory is renamed or moved. If you decide that the
English name for the `Photos` directory is annoying and you want to
- use the the Finnish `Valokuvat` instead, you can rename that in an
+ use the Finnish `Valokuvat` instead, you can rename that in an
instant. However, without de-duplication, you then have to backup
all your photos again.
* When all a team works on the same things, and everyone has copies of
diff --git a/obnam.1.in b/obnam.1.in
index dde04e17..2ad835ff 100644
--- a/obnam.1.in
+++ b/obnam.1.in
@@ -373,7 +373,7 @@ If the backup frequency was once per day,
.B obnam
would keep the backup of each calendar hour for which a backup was made,
for 72 such backups.
-In other words, it would effectively keep the the last 72 daily backups.
+In other words, it would effectively keep the last 72 daily backups.
.PP
Sound confusing?
Just wonder how confused the developer was when writing the code.