Merge pull request #786 from oracle/edits

clean-up odds and ends

Author: rjeberhard

README.md

@@ -18,7 +18,7 @@ Oracle is finding ways for organizations using WebLogic Server to run important
 * Scale WebLogic domains by starting and stopping Managed Servers on demand, or by integrating with a REST API to initiate scaling based on WLDF, Prometheus, Grafana, or other rules.
 * Publish operator and WebLogic Server logs into Elasticsearch and interact with them in Kibana.
 
-The fastest way to experience the operator is to follow the [Quick start guide](site/quickstart.md), or you can peruse our [documentation](site), read our [blogs](https://blogs.oracle.com/weblogicserver/how-to-weblogic-server-on-kubernetes), or try out the [samples](kubernetes/samples/README.md).
+The fastest way to experience the operator is to follow the [Quick Start guide](site/quickstart.md), or you can peruse our [documentation](site), read our [blogs](https://blogs.oracle.com/weblogicserver/how-to-weblogic-server-on-kubernetes), or try out the [samples](kubernetes/samples/README.md).
 
 ```diff
 + The current release of the operator is 2.0-rc2, a release candidate for our 2.0 release.
@@ -54,7 +54,7 @@ maintained for one release after a replacement is available.
 This documentation includes sections targeted to different audiences.  To help you find what you are looking for more easily,
 please consult this table of contents:
 
-* The [Quick start guide](site/quickstart.md) explains how to quickly get the operator running, using the defaults, nothing special.
+* The [Quick Start guide](site/quickstart.md) explains how to quickly get the operator running, using the defaults, nothing special.
 * The [User guide](site/user-guide.md) contains detailed usage information, including how to install and configure the operator,
   and how to use it to create and manage WebLogic domains.  
 * The [Samples](kubernetes/samples/README.md) provide detailed example code and instructions that show you how to perform

kubernetes/samples/scripts/create-weblogic-domain-pv-pvc/README.md

@@ -6,8 +6,7 @@ A PV and PVC can be shared by multiple WebLogic domains or dedicated to a partic
 
 ## Prerequisites
 
-Please read this guide before proceeding.
-* [Persistent Volumes](../../../../site/persistent-volumes.md)
+Please read the [Persistent Volumes](../../../../site/persistent-volumes.md) guide before proceeding.
 
 ## Using the scripts to create a PV and PVC  
 

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/README.md

@@ -4,7 +4,7 @@ The sample scripts demonstrate the creation of a WebLogic domain home in a Docke
 
 ## Prerequisites
 
-Before you begin, read this guide, [Domain Resource](../../../../../site/domain-resource.md)
+Before you begin, read this guide, [Domain Resource](../../../../../site/domain-resource.md).
 
 The following prerequisites must be handled prior to running the create domain script:
 * The WDT sample requires that `JAVA_HOME` is set to a Java JDK version 1.8 or later.
@@ -306,7 +306,7 @@ Spec:
       Name:   JAVA_OPTIONS
       Value:  -Dweblogic.StdoutDebugEnabled=false
       Name:   USER_MEM_ARGS
-      Value:  -Xms64m -Xmx256m 
+      Value:  -Xms64m -Xmx256m
     Labels:
     Liveness Probe:
     Node Selector:

kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md

@@ -4,7 +4,7 @@ The sample scripts demonstrate the creation of a WebLogic domain home on an exis
 
 ## Prerequisites
 
-Before you begin, read this guide, [Domain Resource](../../../../../site/domain-resource.md)
+Before you begin, read this guide, [Domain Resource](../../../../../site/domain-resource.md).
 
 The following prerequisites must be handled prior to running the create domain script:
 * Make sure the WebLogic operator is running.
@@ -280,7 +280,7 @@ Spec:
       Name:   JAVA_OPTIONS
       Value:  -Dweblogic.StdoutDebugEnabled=false
       Name:   USER_MEM_ARGS
-      Value:  -Xms64m -Xmx256m 
+      Value:  -Xms64m -Xmx256m
     Labels:
     Liveness Probe:
     Node Selector:

site/domain-resource.md

@@ -1,6 +1,6 @@
 # Domain resource
 
-In this guide, we outline how to set up and configure your own domain resource which can be used to configure your WLS domain. Then, you can use the domain resource to start the Kubernetes artifacts of the corresponding domain. 
+In this guide, we outline how to set up and configure your own domain resource which can be used to configure your WLS domain. Then, you can use the domain resource to start the Kubernetes artifacts of the corresponding domain.
 
 Swagger documentation is available [here](https://oracle.github.io/weblogic-kubernetes-operator/domains/index.html).
 
@@ -15,7 +15,7 @@ The following prerequisites must be fulfilled before proceeding with the creatio
 
 Domain resources are defined using the domain resource YAML files. For each WLS domain you want to create and configure, you should create one domain resource YAML file and apply it. In the example below, you will find a domain resource YAML file template that you can use as a basis. Copy the template and override the default settings so that it matches all the WLS domain parameters that define your WLS domain.
 
-For sample YAML templates, see the [Domain resource example](../kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md)
+For sample YAML templates, see the [Domain resource example](../kubernetes/samples/scripts/create-weblogic-domain/domain-home-on-pv/README.md).
 
 # Kubernetes resources
 

site/domains.md

@@ -80,7 +80,9 @@ running in Kubernetes.
   administration port or a T3 channel to allow WLST access, you need to ensure that you allocate each channel a
   unique port number across the entire Kubernetes cluster.  If you expose the administration port in each WebLogic domain in
   the Kubernetes cluster, then each one must have a different port.  This is required because `NodePorts` are used to
-  expose channels outside the Kubernetes cluster.  **IMPORTANT:** Exposing admin, RMI, or T3 capable channels via a node port
+  expose channels outside the Kubernetes cluster.  
+
+  **IMPORTANT:** Exposing admin, RMI, or T3 capable channels via a node port
   can create an insecure configuration; in general only HTTP protocols should be made available externally and this exposure
   is usually accomplished by setting up an external load balancer that can access internal (non-NodePort) services.
 * _Host Path Persistent Volumes:_ If using a `hostPath` persistent volume, then it must be available on all worker nodes in the cluster and have read/write/many permissions for all container/pods in the WebLogic Server deployment.  Be aware
@@ -118,7 +120,7 @@ More information about the Domain resource can be found [here](domain-resource.m
 ### Managing lifecycle operations including shutting down and deleting domains
 
 In Operator 2.0, you can perform lifecycle operations on WebLogic servers, clusters, or domains.
-See [Starting, stopping and restarting servers](server-lifecycle.md).
+See [Starting, stopping, and restarting servers](server-lifecycle.md).
 
 ### Scaling clusters
 

site/helm-charts.md

@@ -81,15 +81,15 @@ The script takes the subject alternative names that should be added to the certi
 $ kubernetes/samples/scripts/rest/generate-external-rest-identity.sh "DNS:${HOSTNAME},DNS:localhost,IP:127.0.0.1" >> custom-values.yaml
 ```
 
-## Optional: ELK (Elasticsearch, Logstash and Kibana) integration
+## Optional: Elastic Stack (Elasticsearch, Logstash, and Kibana) integration
 
-The operator Helm chart includes the option of installing the necessary Kubernetes resources for ELK integration.
+The operator Helm chart includes the option of installing the necessary Kubernetes resources for Elastic Stack integration.
 
 You are responsible for configuring Kibana and Elasticsearch, then configuring the operator Helm chart to send events to Elasticsearch. In turn, the operator Helm chart configures Logstash in the operator deployment to send the operator's log contents to that Elasticsearch location.
 
-### ELK per-operator configuration
+### Elastic Stack per-operator configuration
 
-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:
+As part of the Elastic Stack 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`).
@@ -268,11 +268,11 @@ domainNamespaces: [ "namespace1", "namespace2" ]
 
 **NOTE**: These examples show two valid YAML syntax options for arrays.
 
-### ELK integration
+### Elastic Stack integration
 
 #### `elkIntegrationEnabled`
 
-Specifies whether or not ELK integration is enabled.
+Specifies whether or not Elastic Stack integration is enabled.
 
 Defaults to `false`.
 

site/quickstart.md

@@ -1,6 +1,6 @@
-# Quick start guide
+# Quick Start guide
 
-Use this quick start guide to create a WebLogic deployment in a Kubernetes cluster with the Oracle WebLogic Kubernetes Operator. Please note that this walk-through is for demonstration purposes only, not for use in production.
+Use this Quick Start guide to create a WebLogic deployment in a Kubernetes cluster with the Oracle WebLogic Kubernetes Operator. Please note that this walk-through is for demonstration purposes only, not for use in production.
 These instructions assume that you are already familiar with Kubernetes.  If you need more detailed instructions, please
 refer to the [User guide](user-guide.md).
 

site/recent-changes.md

@@ -4,7 +4,7 @@ This document tracks recent changes to the operator, especially ones that introd
 
 | Date | Version | Introduces backward incompatibilities | Change |
 | --- | --- | --- | --- |
-| January 17, 2019 | v2.0-rc2 | yes | Schema updates are completed, and various bug fixes.
+| January 17, 2019 | v2.0-rc2 | yes | Schema updates are completed, and various bugs fixed.
 | December 20, 2018 | v2.0-rc1 | yes | Operator is now installed via Helm charts, replacing the earlier scripts.  The operator now supports the domain home on persistent volume or in Docker image use cases, which required a redesign of the domain schema.  You can override the domain configuration using configuration override templates.  Now load balancers and Ingresses can be independently configured.  You can direct WebLogic logs to a persistent volume or to the pod's log.  Added lifecycle support for servers and significantly enhanced configurability for generated pods.  The final v2.0 release will be the initial release where the operator team intends to provide backward compatibility as part of future releases.
 | March 20, 2018 | v1.1 | yes | Several files and input parameters have been renamed.  This affects how operators and domains are created.  It also changes generated Kubernetes artifacts, therefore customers must recreate their operators and domains.
 | April 4, 2018 | v1.0 | yes | Many Kubernetes artifact names and labels have changed. Also, the names of generated YAML files for creating a domain's PV and PVC have changed.  Because of these changes, customers must recreate their operators and domains.

site/weblogic-docker-images.md

@@ -10,7 +10,7 @@ There are two main options available:
 
 If you want to use the first option, you will need to obtain the standard
 WebLogic Server image from the Docker Store, [see here](#obtaining-standard-images-from-the-docker-store),
-and then create a new image with the mandatory patches applied as described in [this section](#creating-a-custom-images-with-patches-applied).
+and then create a new image with the mandatory patches applied as described in [this section](#creating-a-custom-image-with-patches-applied).
 If you want to use additional patches, you can customize that process to include additional patches.
 
 If you want to use the second option, which includes the domain directory