edits

Author: rosemarymarano

kubernetes/samples/scripts/elasticsearch-and-kibana/README.md

@@ -1,23 +1,21 @@
 # Sample to deploy Elasticsearch and Kibana
 
 
-When a user installs the WebLogic operator Helm chart, the user can set
-`elkIntegrationEnabled` to `true` in their `values.yaml` to tell the operator to send the
-contents of the operator's logs to Elasticsearch.
+When you install the WebLogic operator Helm chart, you can set
+`elkIntegrationEnabled` to `true` in your `values.yaml` file to tell the operator to send the contents of the operator's logs to Elasticsearch.
 
-Typically, a user would have already configured Elasticsearch and Kibana in the
-Kubernetes cluster, and also would specify `elasticSearchHost` and `elasticSearchPort`
-in their `values.yaml` file to point to where Elasticsearch is already running.
+Typically, you would have already configured Elasticsearch and Kibana in the
+Kubernetes cluster, and also would have specified `elasticSearchHost` and `elasticSearchPort` in your `values.yaml` file to point to where Elasticsearch is already running.
 
 This sample configures the Elasticsearch and Kibana deployments and services.
 It's useful for trying out the operator in a Kubernetes cluster that doesn't already
 have them configured.
 
-It runs Elasticstack on the same host and port that the operator's Helm chart defaults
-to, therefore, the customer only needs to set `elkIntegrationEnabled` to `true` in their
+It runs the Elastic Stack on the same host and port that the operator's Helm chart defaults
+to, therefore, you only need to set `elkIntegrationEnabled` to `true` in your
 `values.yaml` file.
 
-To install ElasticSearch and Kibana, use:
+To install Elasticsearch and Kibana, use:
 ```
 $  kubectl apply -f kubernetes/samples/scripts/elasticsearch-and-kibana/elasticsearch_and_kibana.yaml
 ```

site/helm-charts.md

@@ -4,18 +4,18 @@
 
 The WebLogic Kubernetes Operator uses Helm to create and deploy any necessary resources and then run the operator in a Kubernetes cluster. Helm helps you manage Kubernetes applications. Helm charts help you define and install applications into the Kubernetes cluster. The operator's Helm chart is located in the `kubernetes/charts/weblogic-operator` directory.
 
-> If you have an old version of the operator installed on your cluster you must remove
-  it before installing this version.  You should remove the deployment (for example `kubectl delete deploy weblogic-operator -n your-namespace`) and the custom
-  resource definition (for example `kubectl delete crd domain`).  If you do not remove
-  the custom resource definition you may see errors like this: 
-  
-    `Error from server (BadRequest): error when creating "/scratch/output/uidomain/weblogic-domains/uidomain/domain.yaml": 
+> If you have an older version of the operator installed on your cluster, then you must remove
+  it before installing this version.  You should remove the deployment (for example, `kubectl delete deploy weblogic-operator -n your-namespace`) and the custom
+  resource definition (for example, `kubectl delete crd domain`).  If you do not remove
+  the custom resource definition, then you might see errors like this:
+
+    `Error from server (BadRequest): error when creating "/scratch/output/uidomain/weblogic-domains/uidomain/domain.yaml":
     the API version in the data (weblogic.oracle/v2) does not match the expected API version (weblogic.oracle/v1`
 
 
 ## Install Helm and Tiller
 
-Helm has two parts: a client (helm) and a server (tiller). Tiller runs inside of your Kubernetes cluster, and manages releases (installations) of your charts.  See https://github.com/kubernetes/helm/blob/master/docs/install.md for detailed instructions on installing helm and tiller.
+Helm has two parts: a client (Helm) and a server (Tiller). Tiller runs inside of your Kubernetes cluster, and manages releases (installations) of your charts.  See https://github.com/kubernetes/helm/blob/master/docs/install.md for detailed instructions on installing Helm and Tiller.
 
 ## Operator's Helm chart configuration
 
@@ -69,7 +69,7 @@ You are responsible for configuring Kibana and Elasticsearch, then configuring t
 As part of the ELK integration, Logstash configuration occurs for each deployed operator instance.  You can use the following configuration values to configure the integration:
 
 * Set `elkIntegrationEnabled` is `true` to enable the integration.
-* Set `logStashImage` to override the default version of logstash to be used (`logstash:6.2`).
+* Set `logStashImage` to override the default version of Logstash to be used (`logstash:6.2`).
 * Set `elasticSearchHost` and `elasticSearchPort` to override the default location where Elasticsearch is running (`elasticsearch2.default.svc.cluster.local:9201`). This will configure Logstash to send the operator's log contents there.
 
 More detailed information about configuration values can be found in [Operator Helm configuration values](#operator-helm-configuration-values).
@@ -146,7 +146,7 @@ Show the history of the operator Helm release:
 $ helm history weblogic-operator
 ```
 
-Roll back to a previous version of this operator Helm release, in this case the first version:
+Roll back to a previous version of this operator Helm release, in this case, the first version:
 ```
 $ helm rollback weblogic-operator 1
 ```
@@ -226,7 +226,7 @@ imagePullSecrets:
 
 #### `domainNamespaces`
 
-Specifies a list of WebLogic domain namespaces which the operator manages. The names must be lower case. You are responsible for creating these namespace.
+Specifies a list of WebLogic domain namespaces which the operator manages. The names must be lower case. You are responsible for creating these namespaces.
 
 This property is required.
 
@@ -297,7 +297,7 @@ Determines whether the operator's REST interface will be exposed outside the Kub
 
 Defaults to `false`.
 
-If set to true, the user must provide the SSL certificate and private key for the operator's external REST interface by specifying the `externalOperatorCert` and `externalOperatorKey` properties.
+If set to `true`, you must provide the SSL certificate and private key for the operator's external REST interface by specifying the `externalOperatorCert` and `externalOperatorKey` properties.
 
 Example:
 ```
@@ -318,11 +318,11 @@ externalRestHttpsPort: 32009
 
 #### externalOperatorCert
 
-Specifies the user supplied certificate to use for the external operator REST HTTPS interface. The value must be a string containing a Base64 encoded PEM certificate. This parameter is required if `externalRestEnabled` is true, otherwise, it is ignored.
+Specifies the user supplied certificate to use for the external operator REST HTTPS interface. The value must be a string containing a Base64 encoded PEM certificate. This parameter is required if `externalRestEnabled` is `true`, otherwise, it is ignored.
 
 There is no default value.
 
-The helm installation will produce an error, similar to the following, if `externalOperatorCert` is not specified (left blank) and `externalRestEnabled` is true:
+The Helm installation will produce an error, similar to the following, if `externalOperatorCert` is not specified (left blank) and `externalRestEnabled` is `true`:
 ```
 Error: render error in "weblogic-operator/templates/main.yaml": template: weblogic-operator/templates/main.yaml:4:3: executing "weblogic-operator/templates/main.yaml"
   at <include "operator.va...>: error calling include: template: weblogic-operator/templates/_validate-inputs.tpl:53:4: executing "operator.validateInputs"
@@ -341,7 +341,7 @@ Specifies user supplied private key to use for the external operator REST HTTPS
 
 There is no default value.
 
-The helm installation will produce an error, similar to the following, if `externalOperatorKey` is not specified (left blank) and `externalRestEnabled` is true:
+The Helm installation will produce an error, similar to the following, if `externalOperatorKey` is not specified (left blank) and `externalRestEnabled` is `true`:
 ```
 Error: render error in "weblogic-operator/templates/main.yaml": template: weblogic-operator/templates/main.yaml:4:3: executing "weblogic-operator/templates/main.yaml"
   at <include "operator.va...>: error calling include: template: weblogic-operator/templates/_validate-inputs.tpl:53:4: executing "operator.validateInputs"
@@ -438,13 +438,13 @@ The `helm upgrade` succeeds, and silently adopts the resources the first operato
 
 For example, if you delete this release, then the first operator will get messed up because the role binding it needs is gone. The big problem is that you don't get a warning, so you don't know that there's a problem to fix.
 
-This can be fixed by just upgrading the helm release.
+This can be fixed by just upgrading the Helm release.
 
-This may also be fixed by rolling back the helm release.
+This may also be fixed by rolling back the Helm release.
 
 ### Installing an operator and telling it to use the same external REST port number as another operator
 
-A new `FAILED` helm release is created.
+A new `FAILED` Helm release is created.
 ```
 $ helm install --no-hooks --name op2 --namespace myuser-op2-ns --values o.yaml kubernetes/charts/weblogic-operator
 Error: release op2 failed: Service "external-weblogic-operator-svc" is invalid: spec.ports[0].nodePort: Invalid value: 31023: provided port is already allocated
@@ -462,8 +462,8 @@ $ helm upgrade --no-hooks --values o23.yaml op2 kubernetes/charts/weblogic-opera
 Error: UPGRADE FAILED: Service "external-weblogic-operator-svc" is invalid: spec.ports[0].nodePort: Invalid value: 31023: provided port is already allocated
 ```
 
-You can fix this by upgrading the helm release (to fix the port number).
-You can also fix this by rolling back the helm release.
+You can fix this by upgrading the Helm release (to fix the port number).
+You can also fix this by rolling back the Helm release.
 
 ### Installing an operator and telling it to use a service account that doesn't exist
 
@@ -503,7 +503,7 @@ To recover:
 
 ### Installing an operator and telling it to manage a domain namespace that doesn't exist
 
-A new 'FAILED' helm release is created.
+A new `FAILED` Helm release is created.
 ```
 $ helm install --no-hooks --name op2 --namespace myuser-op2-ns --values o.yaml kubernetes/charts/weblogic-operator
 Error: release op2 failed: namespaces "myuser-d2-ns" not found