aboutsummaryrefslogtreecommitdiff
path: root/man/backupninja.1
diff options
context:
space:
mode:
authorintrigeri <intrigeri@boum.org>2010-05-30 19:35:52 +0200
committerintrigeri <intrigeri@boum.org>2010-05-30 19:36:42 +0200
commit211d6506cbde8091cb0d6574bb43515cf916166b (patch)
tree691a58c0f6463b00c71a6a3c3e1fb8b2f337902a /man/backupninja.1
parent4015b1b2620f9e44a32a552cd274a902f2f913cb (diff)
downloadbackupninja-211d6506cbde8091cb0d6574bb43515cf916166b.tar.gz
backupninja-211d6506cbde8091cb0d6574bb43515cf916166b.tar.bz2
Fix typo in manpage (Closes: #583778)
Diffstat (limited to 'man/backupninja.1')
-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