aboutsummaryrefslogtreecommitdiff
path: root/man
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2010-08-26 02:04:13 +0200
committerintrigeri <intrigeri@boum.org>2010-08-26 02:04:13 +0200
commit93041732b3ccffa113693af8480d69fc080d9ec1 (patch)
treeb2950b49cba6a22b448a7e88819c2ac6c26847ad /man
parente6c65815c8201d123f477e05a367832204c39886 (diff)
parent40155781065eb7254eb9fc9c48bd85b0b8ace4c0 (diff)
downloadbackupninja-93041732b3ccffa113693af8480d69fc080d9ec1.tar.gz
backupninja-93041732b3ccffa113693af8480d69fc080d9ec1.tar.bz2
Merge branch 'master' into debian
Conflicts: examples/example.ldap
Diffstat (limited to 'man')
-rw-r--r--man/backupninja.12
1 files changed, 1 insertions, 1 deletions
diff --git a/man/backupninja.1 b/man/backupninja.1
index 53b1e3c..5622881 100644
--- a/man/backupninja.1
+++ b/man/backupninja.1
@@ -96,7 +96,7 @@ To preform the actual backup actions, backupninja processes each action configur
.SH EXAMPLE USAGE
.TP
-Backupninja can be used to impliment whatever backup strategy you choose. It is intended, however, to be used like so:
+Backupninja can be used to implement whatever backup strategy you choose. It is intended, however, to be used like so:
.TP
First, databases are safely copied or exported to /var/backups. Often, you cannot make a file backup of a database while it is in use, hence the need to use special tools to make a safe copy or export into /var/backups.
.TP