anchor.diff:  
   This project aims to provide simple conventions and support for writing {pre,post}-backup scripts with minimal boilerplate, and also provide some common scripts (e.g. for Btrfs snapshots, PostgreSQL…).
   
  -The first thing we should clarify: this project is _not_ a backup solution.
  +Note this project is *not a backup solution*.
   So what it actually is?
  -Well, many backup solutions, like http://www.bacula.org[Bacula] or just simple rsync, work only with files.
  +Many backup solutions, like http://www.bacula.org[Bacula] or just simple rsync, work only with files.
   The problem is that you often can’t just copy bunch of files from a running system.
  -You need to dump a SQL database, create a snapshot on Btrfs/ZFS/LVM, … to prepare files that will be actually backed up.
  -When the backup is done, then you usually want to remove dumps, destroy snapshots etc.
  -Here comes on the scene PreBackup.
  +You need to dump an SQL database, create a snapshot on Btrfs/ZFS/LVM, … to prepare files that will be actually backed up.
  +Once the backup is done, you usually want to remove dumps, destroy snapshots etc.
  +That’s where PreBackup can help.
   
  -PreBackup is a supplement to a file-oriented backup software, its task is to prepare files to be backed up and do cleanup when it’s done.
  +PreBackup is a supplement to a file-oriented backup software.
  +Its task is to prepare files for back up and do a cleanup when it’s done.
   
  -It was originally written to be used with Bacula, but it’s totally independent from it.
  -The only assumption we have is that a backup software is able to execute some command before and after it do a backup.
  +Originally it was written for Bacula, but it can be used with any backup solution.
  +The only requirement is that your backup software can execute some command before and after a backup.
   
   
   == Installation
  
positive.code: 
  RUN_AS::
    User to run the script.
    If you execute the script as a different user than the one specified by `$RUN_AS`, then it will switch to the specified user using `su`.
    Default is empty, i.e. do not switch user.
  
  SYSLOG::
  
negative.code: * `/etc/bacula/prebackup.conf` – global configuration file (you can modify this path in link:bin/prebackup[]),
  * `./config` – local configuration file located in the same directory as the pair of `pre-backup` and `post-backup` symlinks (or file and symlink) used to run the script for a particular job.
  
  These files are just another shell scripts, but you _should_ define only variables here.
  The files are sourced in the defined order before an actual prebackup script.
  If both files exist and define the same variable, the local config overrides the global.
  
  
  == Predefined Variables
  