OWLS-66103, Additional documentation based on review

Author: jgrundback

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

@@ -4,11 +4,10 @@ The sample scripts demonstrate the creation of a WebLogic domain home on an exis
 
 ## Prerequisites
 
-Please read this guide before proceeding.
-* [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.
+* Make sure the WebLogic operator is running.
 * Create a Kubernetes namespace for the domain unless the intention is to use the default namespace.
 * In the same Kubernetes namespace, create the Kubernetes persistent volume where the domain home will be hosted, and the Kubernetes persistent volume claim for the domain. For samples to create a PV and PVC, refer to [Create sample PV and PVC](../../create-weblogic-domain-pv-pvc/README.md).
 * Create the Kubernetes secrets `username` and `password` of the admin account in the same Kubernetes namespace as the domain.
@@ -138,7 +137,7 @@ spec:
   domainHome: /shared/domains/domain1
   # If the domain home is in the image
   domainHomeInImage: false
-  # The Operator currently does not support other images
+  # The operator currently does not support other images
   image: "store/oracle/weblogic:19.1.0.0"
   # imagePullPolicy defaults to "Always" if image version is :latest
   imagePullPolicy: "IfNotPresent"
@@ -161,7 +160,7 @@ spec:
   # will be stored in the default logHome location of /shared/logs/<domainUID>/.
   logHome: /shared/logs/domain1
   # serverStartPolicy legal values are "NEVER", "ALWAYS", "IF_NEEDED", or "ADMIN_ONLY"
-  # This determines which WebLogic Servers the Operator will start up when it discovers this Domain
+  # This determines which WebLogic Servers the operator will start up when it discovers this Domain
   # - "ALWAYS" will start up all defined servers
   # - "ADMIN_ONLY" will start up only the administration server (no managed servers will be started)
   # - "IF_NEEDED" will start all non-clustered servers, including the administration server and clustered servers up to the replica count

site/domain-resource.md

@@ -1,21 +1,20 @@
 
-# Domain Resource
+# 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. The domain resource which can then be used 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. 
 
 ## Prerequisites
 
 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 custom resource unless the intention is to use the default namespace.
-* Create the Kubernetes secrets `username` and `password` of the admin account in the same Kubernetes namespace as the domain custom 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.
+* Create the Kubernetes secrets `username` and `password` of the admin account in the same Kubernetes namespace as the domain resource.
 
 # YAML files
 
-Domain resources are defined via Domain Custom Resource YAML files. For each WLS domain you want to create and configure, you should create one Domain Custom Resource YAML file and apply it. In the example below, you will find a Domain Custom 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.
+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, please refer to this example.
-* [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
 
@@ -28,7 +27,7 @@ After you have written your YAML files, please use them to create your WLS domai
 
 ## Verify the results
 
-To confirm that the domain custom resource was created, use this command:
+To confirm that the domain resource was created, use this command:
 
 ```
 kubectl describe domain [domain name] -n [namespace]