Cleaned up layout

docs/scheduling-backups.md

@@ -4,7 +4,8 @@ Regular backups should be scheduled using `cron(8)` or similar command
 scheduling service on the backup host. The backup frequency will dictate the
 worst case [recovery point objective (RPO)][1] in your backup plan. We recommend
 hourly backups at the least.
-## Example scheduling usage
+
+## Example scheduling of backups
 
 The following examples assume the Backup Utilities are installed under
 `/opt/backup-utils`. The crontab entry should be made under the same user that
@@ -32,13 +33,14 @@ MAILTO=admin@example.com
 0 0 * * * /opt/backup-utils/bin/ghe-backup -v 1>>/opt/backup-utils/backup.log 2>&1
 ```
 
-### Example snapshot pruning 
+## Example snapshot pruning 
 
 By default all expired and incomplete snapshots are deleted at the end of the main
 backup process `ghe-backup`. If pruning these snapshots takes a long time you can
 choose to disable the pruning process from the backup run and schedule it separately.
 This can be achieved by enabling the `GHE_PRUNING_SCHEDULED` option in `backup.config`.
-Please note that this option is only avilable for `backup-utils` >= v3.10.0, if this option is enabled you will need to schedule the pruning script `ghe-prune-snapshots` using `cron` or a similar command scheduling service on the backup host.
+Please note that this option is only avilable for `backup-utils` >= `v3.10.0`.
+If this option is enabled you will need to schedule the pruning script `ghe-prune-snapshots` using `cron` or a similar command scheduling service on the backup host.
 
 To schedule daily snapshot pruning, use: