tweak docs

Author: Jeff McCormick

README.asciidoc

@@ -15,25 +15,33 @@ v1.4, {docdate}
 
 The PostgreSQL Operator provides a Kubernetes operator capability for managing PostgreSQL Clusters deployed within a Kubernetes.
 
-The PostgreSQL Operator leverages Kubernetes Third Party Resources to define custom resource type *pgcluster*, *pgbackups*, and *pgupgrades*.
+The PostgreSQL Operator leverages Kubernetes Third Party Resources to define custom resource types such as:
+
+ * *pgcluster* 
+ * *pgbackups*
+ * *pgupgrades*
+ * *pgclones*
+ * *pgpolicies*
+ * *pgpolicylogs*
+ 
 
 Once those custom objects are defined, Kubernetes provides the ability to create and manage those objects similar to any other native Kubernetes object.
 
-The PostgreSQL Operator runs within Kubernetes detecting these new custom object types being created or removed.
+The PostgreSQL Operator runs within Kubernetes detecting these new custom object types being created, updated, or removed.
 
 Once the objects are detected, the PostgreSQL Operator enables users to perform operations across the Kubernetes environment, including:
 
-* Create Cluster
-* Destroy Cluster
-* Backup Cluster
-* Scale a Cluster
-* Restore Cluster
-* Upgrade Cluster
+* Create a PostgreSQL Cluster
+* Destroy a PostgreSQL Cluster
+* Backup a PostgreSQL Cluster
+* Scale a a PostgreSQL Cluster
+* Restore a PostgreSQL Cluster
+* Upgrade a PostgreSQL Cluster
 * View PVC
-* Test Connections
-* Clone a Cluster
-* Create a Policy
-* Apply a Policy
+* Test Connections to a PostgreSQL Cluster
+* Clone a PostgreSQL Cluster
+* Create a SQL-based Policy
+* Apply a SQL-based Policy to a PostgreSQL Cluster
 
 What actually gets created on the Kube cluster for a
 *pgcluster* resource is defined as a *deployment strategy*.  Strategies
@@ -167,8 +175,8 @@ or modifying PostgreSQL databases deployed within the Kube cluster.
 
 image::docs/operator-diagram.png?raw=true[]
 
-The operator functionality runs in a Pod deployed to your
-Kubernetes cluster.  The *postgres-operator* Docker container
+The operator functionality runs in a Kubernetes Deployment on your
+Kubernetes cluster.  The *postgres-operator* Docker container image
 is available on link:https://hub.docker.com/r/crunchydata/postgres-operator/[Dockerhub].
 
 You can also build the Docker image for *postgres-operator* using

docs/build.asciidoc

@@ -78,7 +78,14 @@ kubectl create clusterrolebinding permissive-binding \
 See https://kubernetes.io/docs/admin/authorization/rbac/ for more
 details on how to enable RBAC roles.
 
-To test the *postgres-operator* you will need a Kubernetes cluster
+To test the *postgres-operator* you will need a Kubernetes cluster.
+
+In testing, I've found that specifying GOMAXPROCS to equal your number
+of CPUs when executing Kubernetes is preferable, for example:
+
+....
+export GOMAXPROCS=4
+....
 
 [#Openshift Origin Environment]
 == Openshift Origin Environment

docs/design.asciidoc

@@ -14,8 +14,10 @@ of the postgres Operator to define:
  * Cluster - *pgclusters*
  * Backup - *pgbackups*
  * Upgrade - *pgupgrades*
+ * Clones - *pgclones*
+ * Policy - *pgpolicies*
 
-A Cluster is made up of multiple Pods, Services, and Proxies.
+A PostgreSQL Cluster is made up of multiple Deployments, Services, and Proxies.
 
 
 == Command Line Interface
@@ -35,8 +37,8 @@ not created by the Crunchy Operator are now viewable from the CLI.
 
 == Operator Deployment
 
-The postgres Operator runs within a Pod Deployment in the Kubernetes
-cluster.  An administrator will deploy the postgres Operator pod
+The postgres Operator runs within a Deployment in the Kubernetes
+cluster.  An administrator will deploy the postgres Operator Deployment
 using the provided script.  Once installed and running, the Operator
 pod will start watching for certain defined events.