Merge pull request #328 from xenophenes/pre32

update pgouser file information, update pgo.yaml.dynamic -> storageclass

Author: jmccormick2001

hugo/content/installation/configuration.adoc

@@ -79,8 +79,9 @@ $COROOT/conf/apiserver/pgouser
 
 The sample configuration for `pgouser` is as follows -
 ....
-username:password
-testuser:testpass
+username:password:pgoadmin
+testuser:testpass:pgoadmin
+readonlyuser:testpass:pgoreader
 ....
 
 Modify these values to be unique to your environment.
@@ -362,7 +363,7 @@ There are currently 3 sample pgo configuration files provided
 for users to use as a starting configuration -
 
  * `pgo.yaml.nfs` - this configuration specifies *create* storage to be used, this is used for NFS storage for example where you want to have a unique PVC created for each database
- * `pgo.yaml.dynamic` - this configuration specifies *dynamic* storage to be used, namely a *storageclass* that refers to a dynamic provisioning strorage such as StorageOS or Portworx, or GCE.
+ * `pgo.yaml.storageclass` - this configuration specifies *dynamic* storage to be used, namely a *storageclass* that refers to a dynamic provisioning strorage such as StorageOS or Portworx, or GCE.
 
 Note, when Storage Type is *create*, you can specify a storage
 configuration setting of *MatchLabels*, when set, this will cause a

hugo/content/installation/deployment.adoc

@@ -58,7 +58,7 @@ export PGO_CLIENT_CERT=$COROOT/conf/apiserver/server.crt
 export PGO_CLIENT_KEY=$COROOT/conf/apiserver/server.key
 ....
 
-The pgo client uses Basic Authentication to authenticate to the operator REST API, for authentication, add the following `.pgouser` file to your $HOME -
+The pgo client uses Basic Authentication to authenticate to the operator REST API. For authentication, add the following `.pgouser` file to your $HOME -
 ....
 echo "username:password" > $HOME/.pgouser
 ....