minor edits

rosemarymarano · rjeberhard · commit 68e07daeef0f · 2019-03-20T08:58:11.000-04:00
diff --git a/docs-source/content/quickstart/cleanup.md b/docs-source/content/quickstart/cleanup.md
@@ -13,7 +13,7 @@ weight: 7
     ```bash
     $ helm delete --purge sample-domain1-ingress
     ```
-1.	Remove the domain resources by using the sample [`delete-weblogic-domain-resources`](http://github.com/oracle/weblogic-kubernetes-operator/blob/master/kubernetes/samples/scripts/delete-domain/delete-weblogic-domain-resources.sh) script.
+1.	Remove the domain resources by using the sample [`delete-weblogic-domain-resources`](http://github.com/oracle/weblogic-kubernetes-operator/blob/master/kubernetes/samples/scripts/delete-domain/delete-weblogic-domain-resources.sh) script:
 
     ```bash
     $ kubernetes/samples/scripts/delete-domain/delete-weblogic-domain-resources.sh -d sample-domain1
diff --git a/docs-source/content/samples/simple/domains/domain-home-in-image/_index.md b/docs-source/content/samples/simple/domains/domain-home-in-image/_index.md
@@ -59,9 +59,9 @@ The script will perform the following steps:
 * Build a Docker image based on the Docker sample, [Example Image with a WebLogic Server Domain using the Oracle WebLogic Scripting Tooling (WLST)](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-home-in-image) or [Example Image with a WebLogic Server Domain using the Oracle WebLogic Deploy Tooling (WDT)](https://github.com/oracle/docker-images/tree/master/OracleWebLogic/samples/12213-domain-home-in-image-wdt). It will create a sample WebLogic Server domain in the Docker image.
   {{% notice warning %}}
   Oracle strongly recommends storing the image containing the domain home as private
-  in the registry (e.g. Oracle Cloud Infrastructure Registry, Docker Hub, etc.) as
+  in the registry (for example, Oracle Cloud Infrastructure Registry, Docker Hub, and such) as
   this image contains sensitive information about the domain including keys and
-  credentials that are used to access external resources (e.g. datasource password).
+  credentials that are used to access external resources (for example, data source password).
   For more information about
   [domain home in image protection]({{<relref "/security/domain-security/image-protection.md#weblogic-domain-in-docker-image-protection">}}),
   see the ***Security*** section.
diff --git a/docs-source/content/samples/simple/domains/domain-home-on-pv/_index.md b/docs-source/content/samples/simple/domains/domain-home-on-pv/_index.md
@@ -103,8 +103,8 @@ The following parameters can be provided in the inputs file.
 | `productionModeEnabled` | Boolean indicating if production mode is enabled for the domain. | `true` |
 | `serverStartPolicy` | Determines which WebLogic Servers will be started up. Legal values are `NEVER`, `IF_NEEDED`, `ADMIN_ONLY`. | `IF_NEEDED` |
 | `t3ChannelPort` | Port for the T3 channel of the NetworkAccessPoint. | `30012` |
-| `t3PublicAddress` | Public address for the T3 channel.  This should be set to the public address of the Kubernetes cluster.  This would normally be a load balancer address. <p/>For development environments only: In a single server (all-in-one) Kubernetes deployment, this may be set to the address of the master, or at the very least, it must be set to the address of one of the worker nodes. | If not provided, the script will attempt to set it to the IP address of the kubernetes cluster |
-| `weblogicCredentialsSecretName` | Name of the Kubernetes secret for the Administration Server's username and password. If not specified, the value is derived from the `domainUID` as `<domainUID>-weblogic-credentials`. | `domain1-weblogic-credentials` |
+| `t3PublicAddress` | Public address for the T3 channel.  This should be set to the public address of the Kubernetes cluster.  This would normally be a load balancer address. <p/>For development environments only: In a single server (all-in-one) Kubernetes deployment, this may be set to the address of the master, or at the very least, it must be set to the address of one of the worker nodes. | If not provided, the script will attempt to set it to the IP address of the Kubernetes cluster |
+| `weblogicCredentialsSecretName` | Name of the Kubernetes secret for the Administration Server's user name and password. If not specified, the value is derived from the `domainUID` as `<domainUID>-weblogic-credentials`. | `domain1-weblogic-credentials` |
 | `weblogicImagePullSecretName` | Name of the Kubernetes secret for the Docker Store, used to pull the WebLogic Server image. | `docker-store-secret` |
 
 Note that the names of the Kubernetes resources in the generated YAML files may be formed with the value of some of the properties specified in the `create-inputs.yaml` file. Those properties include the `adminServerName`, `clusterName` and `managedServerNameBase`. If those values contain any characters that are invalid in a Kubernetes service name, those characters are converted to valid values in the generated YAML files. For example, an uppercase letter is converted to a lowercase letter and an underscore `("_")` is converted to a hyphen `("-")`.
diff --git a/docs-source/content/samples/simple/storage/_index.md b/docs-source/content/samples/simple/storage/_index.md
@@ -14,7 +14,7 @@ A PV and PVC can be shared by multiple WebLogic domains or dedicated to a partic
 
 #### Prerequisites
 
-Please read the [Persistent storage]({{< relref "/userguide/managing-domains/persistent-storage/_index.md" >}}) document before proceeding.
+Before you begin, read this document, [Persistent storage]({{< relref "/userguide/managing-domains/persistent-storage/_index.md" >}}).
 
 #### Using the scripts to create a PV and PVC  
 
@@ -60,7 +60,7 @@ The PV and PVC creation inputs can be customized by editing the `create-pv-pvc-i
 | `domainUID` | ID of the domain resource to which the generated PV and PVC will be dedicated. Leave it empty if the PV and PVC are going to be shared by multiple domains. | no default |
 | `namespace` | Kubernetes namespace to create the PVC. | `default` |
 | `baseName` | Base name of the PV and PVC. The generated PV and PVC will be `<baseName>-pv` and `<baseName>-pvc` respectively. | `weblogic-sample` |
-| `weblogicDomainStoragePath` | Physical path of the storage for the PV.  When `weblogicDomainStorageType` is set to `HOST_PATH`, this value should be set the to path to the domain storage on the Kubernetes host.  When `weblogicDomainStorageType` is set to NFS, then `weblogicDomainStorageNFSServer` should be set to the IP address or name of the DNS server, and this value should be set to the exported path on that server.  Note that the path where the domain is mounted in the WebLogic containers is not affected by this setting, that is determined when you create your domain. | no default |
+| `weblogicDomainStoragePath` | Physical path of the storage for the PV.  When `weblogicDomainStorageType` is set to `HOST_PATH`, this value should be set the to path to the domain storage on the Kubernetes host.  When `weblogicDomainStorageType` is set to NFS, then `weblogicDomainStorageNFSServer` should be set to the IP address or name of the DNS server, and this value should be set to the exported path on that server.  Note that the path where the domain is mounted in the WebLogic containers is not affected by this setting; that is determined when you create your domain. | no default |
 | `weblogicDomainStorageReclaimPolicy` | Kubernetes PVC policy for the persistent storage. The valid values are: `Retain`, `Delete`, and `Recycle`. | `Retain` |
 | `weblogicDomainStorageSize` | Total storage allocated for the PVC. | `10Gi` |
 | `weblogicDomainStorageType` | Type of storage. Legal values are `NFS` and `HOST_PATH`. If using `NFS`, `weblogicDomainStorageNFSServer` must be specified. | `HOST_PATH` |
@@ -180,7 +180,7 @@ spec:
 
 #### Verify the PV and PVC objects
 
-You can use this command to verify the persistent volume was created, note that the `Status` field
+You can use this command to verify the persistent volume was created. Note that the `Status` field
 should have the value `Bound`, indicating the that persistent volume has been claimed:
 
 ```
diff --git a/docs-source/content/userguide/introduction/_index.md b/docs-source/content/userguide/introduction/_index.md
@@ -2,7 +2,7 @@
 title: "Introduction"
 date: 2019-02-23T16:43:10-05:00
 weight: 2
-description: "Learn about the operator's design, architecture, terms, and prerequisites."
+description: "Learn about the operator's design, architecture, important terms, and prerequisites."
 ---
 {{% children style="h4" description="true" %}}
 
diff --git a/docs-source/content/userguide/introduction/demo.md b/docs-source/content/userguide/introduction/demo.md
@@ -3,7 +3,7 @@ title: "Demo"
 date: 2019-02-23T20:51:59-05:00
 draft: false
 weight: 2
-description: "This video provides a demonstration of the WebLogic Server Kubernetes Operator."
+description: "Watch a video demonstration of the WebLogic Server Kubernetes Operator."
 ---
 
 This video provides a demonstration of the WebLogic Server Kubernetes Operator.
diff --git a/docs-source/content/userguide/introduction/design.md b/docs-source/content/userguide/introduction/design.md
@@ -6,7 +6,7 @@ weight: 4
 description: "The Oracle WebLogic Server Kubernetes Operator (the “operator”) is designed to fulfill a similar role to that which a human operator would fill in a traditional data center deployment.  It contains a set of useful built-in knowledge about how to perform various life cycle operations on a domain correctly."
 ---
 
-The Oracle WebLogic Server Kubernetes Operator (the “operator”) is designed to fulfill a similar role to that which a human operator would fill in a traditional data center deployment.  It contains a set of useful built-in knowledge about how to perform various life cycle operations on a domain correctly.a traditional data center deployment.  It contains a set of useful built-in knowledge about how to perform various life cycle operations on a domain correctly.
+The Oracle WebLogic Server Kubernetes Operator (the “operator”) is designed to fulfill a similar role to that which a human operator would fill in a traditional data center deployment.  It contains a set of useful built-in knowledge about how to perform various life cycle operations on a domain correctly.
 
 Human operators are normally responsible for starting and stopping environments, initiating backups, performing scaling operations, performing manual tasks associated with disaster recovery and high availability needs and coordinating actions with other operators in other data centers.  It is envisaged that the operator will have similar responsibilities in a Kubernetes environment.
 
diff --git a/docs-source/content/userguide/managing-domains/_index.md b/docs-source/content/userguide/managing-domains/_index.md
@@ -25,9 +25,9 @@ Please be aware of the following important considerations for WebLogic domains r
   assume that the domain home is `/shared/domains/DOMAIN_UID`.
   {{% notice warning %}}
   Oracle strongly recommends storing an image containing a WebLogic domain home
-  as private in the registry (e.g. Oracle Cloud Infrastructure Registry, Docker Hub, etc.).
-  A Docker image that contains a WebLogic Domain has sensitive information including
-  keys and credentials that are used access external resources (e.g. datasource password).
+  as private in the registry (for example, Oracle Cloud Infrastructure Registry, Docker Hub, and such).
+  A Docker image that contains a WebLogic domain has sensitive information including
+  keys and credentials that are used access external resources (for example, data source password).
   For more information, see
   [domain home in image protection]({{<relref "/security/domain-security/image-protection.md#weblogic-domain-in-docker-image-protection">}})
   in the ***Security*** section.
diff --git a/docs-source/content/userguide/managing-domains/domain-in-image/base-images/_index.md b/docs-source/content/userguide/managing-domains/domain-in-image/base-images/_index.md
@@ -129,7 +129,7 @@ are provided that demonstrate how to create the image using:
 * [WebLogic Deploy Tooling](https://github.com/oracle/weblogic-deploy-tooling)
   to define the domain.
 
-In these samples you will see a reference to a "base" or `FROM` image.  You should use an image
+In these samples, you will see a reference to a "base" or `FROM` image.  You should use an image
 with the mandatory patches installed as this base image.  This image could be either
 the standard `store/oracle/weblogic:12.2.1.3` pre-patched image or an image you created using the instructions above.
 
diff --git a/docs-source/content/userguide/managing-domains/domain-lifecycle/_index.md b/docs-source/content/userguide/managing-domains/domain-lifecycle/_index.md
@@ -5,6 +5,6 @@ weight = 8
 pre = "<b> </b>"
 +++
 
-Learn how you can start, stop, restart, and scale the domain's servers.
+Learn how to start, stop, restart, and scale the domain's servers.
 
 {{% children style="h4" description="true" %}}
diff --git a/docs-source/content/userguide/managing-domains/domain-lifecycle/restarting.md b/docs-source/content/userguide/managing-domains/domain-lifecycle/restarting.md
@@ -99,7 +99,7 @@ kubectl edit domain <domain name> -n <domain namespace>
 The `edit` command opens a text editor which lets you edit the domain resource in place.
 
 {{% notice note %}}
-Typically, it's better to edit the domain resource directly; otherwise, if you scaled the domain, and you just edit the original `domain.yaml` file and reapply it, you could go back to your old replicas count.
+Typically, it's better to edit the domain resource directly; otherwise, if you scaled the domain, and you edit only the original `domain.yaml` file and reapply it, you could go back to your old replicas count.
 {{% /notice %}}
 
 #### Applying WebLogic Server patches
diff --git a/docs-source/content/userguide/managing-domains/domain-resource.md b/docs-source/content/userguide/managing-domains/domain-resource.md
@@ -14,7 +14,7 @@ Swagger documentation is available [here](/weblogic-kubernetes-operator/swagger/
 
 #### Prerequisites
 
-The following prerequisites must be fulfilled before proceeding with the creation of the resource.
+The following prerequisites must be fulfilled before proceeding with the creation of the resource:
 
 * Make sure the WebLogic operator is running.
 * Create a Kubernetes namespace for the domain resource unless the intention is to use the default namespace.
diff --git a/docs-source/content/userguide/managing-domains/persistent-storage/_index.md b/docs-source/content/userguide/managing-domains/persistent-storage/_index.md
@@ -9,7 +9,7 @@ This document outlines how to set up a Kubernetes persistent volume and persiste
 
 #### Prerequisites
 
-The following prerequisites must be fulfilled before proceeding with the creation of the volume.
+The following prerequisites must be fulfilled before proceeding with the creation of the volume:
 
 * Create a Kubernetes namespace for the persistent volume claim unless the intention is to use the default namespace. Note that a persistent volume claim has to be in the same namespace as the domain resource that uses it.
 * Make sure that all the servers in the WebLogic domain are able to reach the storage location.
@@ -38,7 +38,7 @@ For sample YAML templates, refer to the [Persistent volumes example]({{< relref
 
 ### Kubernetes resources
 
-After you have written your YAML files, you use them to create the persistent volume by creating Kubernetes resources using the `kubectl create -f` command.
+After you have written your YAML files, use them to create the persistent volume by creating Kubernetes resources using the `kubectl create -f` command:
 
 ```
 $ kubectl create -f pv.yaml
diff --git a/docs-source/content/userguide/managing-operators/_index.md b/docs-source/content/userguide/managing-operators/_index.md
@@ -2,7 +2,7 @@
 title: "Manage operators"
 date: 2019-02-23T16:43:38-05:00
 weight: 3
-description: "Helm is used to create and deploy necessary operator resources and to run the operator in a Kubernetes cluster. Use the operator's Helm chart to install and manage the operator"
+description: "Helm is used to create and deploy necessary operator resources and to run the operator in a Kubernetes cluster. Use the operator's Helm chart to install and manage the operator."
 ---
 
 
@@ -92,7 +92,7 @@ For more detailed information, see the [REST interface configuration]({{<relref
 
 For testing purposes, the WebLogic Kubernetes Operator project provides a sample script
 that generates a self-signed certificate and private key for the operator external REST interface.
-The generated certificate and key is stored in a kubernetes `tls secret` and the sample
+The generated certificate and key is stored in a Kubernetes `tls secret` and the sample
 script outputs the corresponding configuration values in YAML format. These values can be added to your custom YAML configuration file, for use when the operator's Helm chart is installed.
 
 {{% notice warning %}}
diff --git a/docs-source/content/userguide/managing-operators/installation/_index.md b/docs-source/content/userguide/managing-operators/installation/_index.md
@@ -13,6 +13,7 @@ then run the operator in a Kubernetes cluster.
 Use the `helm install` command to install the operator Helm chart. As part of this, you must specify a "release" name for the operator.
 
 You can override default configuration values in the operator Helm chart by doing one of the following:
+
 - Creating a custom YAML file containing the values to be overridden, and specifying the `--value` option on the Helm command line.
 - Overriding individual values directly on the Helm command line, using the `--set` option.
 
diff --git a/docs-source/content/userguide/managing-operators/using-the-operator/the-rest-api.md b/docs-source/content/userguide/managing-operators/using-the-operator/the-rest-api.md
@@ -16,7 +16,7 @@ You can access most of the REST services using `GET`, for example:
 
 All of the REST services require authentication.  Callers must pass in a valid token header and a CA certificate file.  Callers should pass in the `Accept:/application/json` header.
 
-To protect against Cross Site Request Forgery (CSRF) attacks, the operator REST API requires that you send in a `X-Requested-By` header when you invoke a REST endpoint that makes a change (for example when you POST to the `/scale` endpoint).  The value is an arbitrary name such as `MyClient`. For example, when using curl:
+To protect against Cross Site Request Forgery (CSRF) attacks, the operator REST API requires that you send in a `X-Requested-By` header when you invoke a REST endpoint that makes a change (for example when you POST to the `/scale` endpoint).  The value is an arbitrary name such as `MyClient`. For example, when using `curl`:
 
 ```
 curl ... -H X-Requested-By:MyClient ... -X POST .../scaling
diff --git a/docs-source/content/userguide/overview/k8s-setup.md b/docs-source/content/userguide/overview/k8s-setup.md
@@ -57,7 +57,7 @@ Follow the basic steps from the  [Terraform Kubernetes installer for Oracle Clou
     cp terraform.example.tfvars terraform.tfvars
     ```
 
-1.  Edit the `terraform.tvfars` file to include values for your tenancy, user, and compartment.  Optionally, edit variables to change the `Shape` of the VMs for your Kubernetes master and workers, and your `etcd` cluster.   For example:
+1.  Edit the `terraform.tvfars` file to include values for your tenancy, user, and compartment.  Optionally, edit the variables to change the `Shape` of the VMs for your Kubernetes master and workers, and your `etcd` cluster.   For example:
 
      ```
      #give a label to your cluster to help identify it if you have multiple
diff --git a/docs-source/content/userguide/overview/prepare.md b/docs-source/content/userguide/overview/prepare.md
@@ -16,12 +16,12 @@ After creating Kubernetes clusters, you can optionally:
 * Configure Kibana and Elasticsearch for your operator logs.
 
 
-#### Load balancing with an Ingress controller or a web server
+#### Load balance with an Ingress controller or a web server
 
 You can choose a load balancer provider for your WebLogic domains running in a Kubernetes cluster. Please refer to the [WebLogic Operator Load Balancer Samples](https://github.com/oracle/weblogic-kubernetes-operator/blob/master/kubernetes/samples/charts/README.md) for information about the current capabilities and setup instructions for each of the supported load balancers.
 
 
-#### Configuring Kibana and Elasticsearch
+#### Configure Kibana and Elasticsearch
 
 You can send the operator logs to Elasticsearch, to be displayed in Kibana. Use
 this [sample script]({{< relref "/samples/simple/elastic-stack/_index.md" >}}) to configure Elasticsearch and Kibana deployments and services.
