Update Readme.md to reflect remote pull method

README.md

@@ -12,7 +12,7 @@ On macOS, it has a few disadvantages compared to Time Machine - in particular it
 
 ## Usage
 
-	Usage: rsync_tmbackup.sh [OPTION]... <SOURCE> <[USER@HOST:]DESTINATION> [exclude-pattern-file]
+	Usage: rsync_tmbackup.sh [OPTION]... <[USER@HOST:]SOURCE> <[USER@HOST:]DESTINATION> [exclude-pattern-file]
 
 	Options
 	 -p, --port           SSH port.
@@ -37,6 +37,11 @@ On macOS, it has a few disadvantages compared to Time Machine - in particular it
 
 		rsync_tmbackup.sh -p 2222 /home user@example.com:/mnt/backup_drive
 
+
+* Backup from remote drive over SSH:
+
+		rsync_tmbackup.shuser@example.com:/home /mnt/backup_drive
+
 * To mimic Time Machine's behaviour, a cron script can be setup to backup at regular interval. For example, the following cron job checks if the drive "/mnt/backup" is currently connected and, if it is, starts the backup. It does this check every 1 hour.
 
 		0 */1 * * * if [[ -d /mnt/backup ]]; then rsync_tmbackup.sh /home /mnt/backup; fi
@@ -70,6 +75,8 @@ To display the rsync options that are used for backup, run `./rsync_tmbackup.sh
 
 * Backup to remote destinations over SSH.
 
+* Backup from remote destinations over SSH.
+
 * Files that haven't changed from one backup to the next are hard-linked to the previous backup so take very little extra space.
 
 * Safety check - the backup will only happen if the destination has explicitly been marked as a backup destination.