Fail if the BACKUP_DIR doesn't exist

[software/bacap.git] / README

diff --git a/README b/README
index 98710af8ad29ee907e73778f8933ebe68eae63fe..7b8f0dd48b8520e0afa1ba42de37096051e881c6 100644 (file)
--- a/README
+++ b/README
@@ -35,8 +35,8 @@ remember: **It's very simple** =)
 
 
 
-Instalation
-===========
+Installation
+============
 
 Doing something very complex in ~100 SLOC_ is not easy, unless you're standing
 in the shoulders of giants. I'm standing in the shoulders of rsync_ mainly, so
@@ -170,11 +170,12 @@ If you are a Debian_ user, you can also simply install the script in
 Providing a ssh_ key
 --------------------
 
-When doing a backup of a remote host, you probably want ssh_ to be able to login
-without providing a password. To do so, you can generate a ssh_ key, copy the
-public key to the target's ``/root/.ssh/authorized_keys`` (or the user that runs
-the backup) and set the Bacap_ configuration variable ``RSYNC_RSH`` to something
-like::
+When doing a backup of a remote host, you probably want ssh_ to be able to
+login without providing a password. To do so, you can generate a ssh_ key using
+``ssh-keygen``, copy the public key to the target's
+``/root/.ssh/authorized_keys`` using ``ssh-copy-id root@host`` (or the user
+that runs the backup) and set the Bacap_ configuration variable ``RSYNC_RSH``
+to something like::
 
        RSYNC_RSH="ssh -i /path/to/priv-key -o NumberOfPasswordPrompts=0"
 
@@ -194,7 +195,7 @@ compression::
 
        RSYNC_RSH="ssh -o Compression=no"
 
-And if your network is trusted, you probably don't need very string encryption
+And if your network is trusted, you probably don't need very strong encryption
 either::
 
        RSYNC_RSH="ssh -o Compression=no -c arcfour"