anchor.diff:  
   === Scheduling
   
  -The `schedule` command will generate schedule configuration maps that are utitlized by the 
  +The `schedule` command will generate schedule configuration maps that are utitlized by the
   link:https://crunchydata.github.io/crunchy-containers/container-specifications/crunchy-scheduler/[crunchy-scheduler]
   container.  This allows users to create automated, scheduled backups for their PostgreSQL clusters.
   
   Currently only two types of backups are supported with the schedule command:
    * pgBackRest
    * pgBaseBackup
  - 
  -Crunchy Scheduler is a cron-like microservice that periodically queries Kubernetes for 
  -configuration maps with the label `crunchy-scheduler=true` in a specific namespace.  
  +
  +Crunchy Scheduler is a cron-like microservice that periodically queries Kubernetes for
  +configuration maps with the label `crunchy-scheduler=true` in a specific namespace.
   After finding the schedule configs, the scheduler service will either exec into the container (pgBackRest) or
   create pgBaseBackup jobs for the configured schedule.
   
  
positive.code:  create a failover state machine which acts as a timer for the cluster.
  If the timer expires, then a failover is triggered on the cluster turning
  one of the cluster replica pods into the replacement primary pod. See the
  link:https://crunchydata.github.io/postgres-operator/how-it-works/[How It Works]
  documentation for more details on auto failover.
  
  ===== pgBackRest
  
negative.code: ....
  
  The pgBackRest backrestrepo PVCs are created using the pgo.yaml `BackupStorage` setting.
  Typically, this will be a RWX file system but if the file system is RWO the PVCs will be
  created without having write access and a backup and restore will fail. The RWX file
  system setup will allow you to restore from this PVC without having to shutdown the currently
  attached PostgreSQL cluster.
  