anchor.diff:  Further details can be found in the link:design.asciidoc[PostgreSQL Operator Design] document on
   how the operator is built and how it operates.
   
  -For most users of the Operator who simply want to deploy 
  +For most users of the Operator who simply want to deploy
   it on a running Kube cluster will find the Quickstart
   script useful https://github.com/CrunchyData/postgres-operator/blob/master/examples/quickstart.sh
   
  
positive.code: ....
  
  This command will cause any cluster matching the selector
  to be removed. 
  
  You can remove a cluster and it's data files by running:
  ....
  
negative.code: |Cluster.Policies        | optional, list of policies to apply to a newly created cluster, comma separated, must be valid policies in the catalog
  |Cluster.PasswordAgeDays        | optional, if set, will set the VALID UNTIL date on passwords to this many days in the future when creating users or setting passwords, defaults to 365 days
  |Cluster.PasswordLength        | optional, if set, will determine the password length used when creating passwords, defaults to 8
  |PrimaryStorage    |required, the value of the storage configuration to use for the primary PostgreSQL deployment
  |BackupStorage    |required, the value of the storage configuration to use for backups
  |ReplicaStorage    |required, the value of the storage configuration to use for the replica PostgreSQL deployments
  |Storage.storage1.StorageClass        |for a dynamic storage type, you can specify the storage class used for storage provisioning(e.g. standard, gold, fast)
  