change per MR

Author: jshum2479

documentation/4.1/content/managing-domains/domain-on-pv/domain-creation-images.md

@@ -71,7 +71,7 @@ For example source locations, see [Configuration example 2](#example-2-source-lo
 If specifying multiple images with model files in their respective `sourceModelHome`
 directories, then model files are merged.
 The operator will merge the model files from multiple images in the same order in which images appear under `model.auxiliaryImages` or `domain.domainCreationImages`.
-Files from later images in the merge overwrite same-named files from earlier images.
+Files from later images take precedence over files from earlier images.
 
 When specifying multiple images, ensure that only one of the images supplies a WDT installation location using
 `sourceWDTInstallHome`.

documentation/4.1/content/managing-domains/domain-on-pv/overview.md

@@ -64,7 +64,7 @@ When you deploy a Domain on PV domain resource YAML file:
 ### Runtime updates
 
 You control runtime updates to the WebLogic domain configuration using tools, such as Fusion Middleware Control, product-specific WLST functions,
-the WebLogic Server Administration Console, the Service Bus Console, or JDeveloper.  After the initial domain is created, subsequent updates to the
+the WebLogic Server Administration Console, the Service Bus Console, WebLogic Remote Console or JDeveloper.  After the initial domain is created, subsequent updates to the
 source of the WDT artifacts or any referenced macros _will be ignored_.  
 
 Some changes may require triggering an introspector job.  For example:

documentation/4.1/content/managing-domains/domain-on-pv/usage.md

@@ -23,13 +23,13 @@ WebLogic domain.
 
 To use this feature, provide the following information:
 
-- [WebLogic base image](#weblogic-base-image) - This is the WebLogic product to be used.
+- [WebLogic base image](#weblogic-base-image) - This is the WebLogic product to be used. For example, WebLogic Server or Fusion Middleware Infrastructure.
 - [Volumes and VolumeMounts information](#volumes-and-volumemounts-information) - This follows the standard Kubernetes pod requirements for mounting persistent volumes.
 - [PersistentVolume and PersistentVolumeClaim](#persistent-volume-and-persistent-volume-claim) - This is environment specific and usually requires assistance from your administrator to provide the underlying details, such as `storageClass` or any permissions.
 - [Domain information](#domain-information) - This describes the domain type and whether the operator should create the RCU schema.
-- [Domain WDT artifacts](#domain-creation-wdt-artifacts) - This is where the WDT binaries and WDT artifacts reside.
-- [Optional WDT artifacts ConfigMap](#optional-wdt-artifacts-configmap) - Optional, WDT artifacts.
-- [Domain resource YAML file]({{< relref "/reference/domain-resource.md">}}) - This is for deploying the domain in WebLogic Kubernetes Operator.
+- [Domain WDT artifacts](#domain-creation-wdt-artifacts) - This is where the WDT binaries, WDT model, WDT archive, and WDT variables files reside.
+- [Optional WDT artifacts ConfigMap](#optional-wdt-artifacts-configmap) - Optional, WDT model, WDT variables files.
+- [Domain resource YAML file]({{< relref "/reference/domain-resource.md">}}) - This is for deploying the domain with WebLogic Kubernetes Operator.
 
 
 - For details about each field,
@@ -79,7 +79,7 @@ The image layout follows this directory structure:
 
 ```
 /auxiliary/weblogic-delpoy - Unzipped WebLogic Deploy Tooling release file.
-/auxiliary/models -  All WDT artifacts, such as model YAML files, model properties, model archives.
+/auxiliary/models -  WDT model, WDT archive, and WDT variables files.
 ```
 
 You can create your own image using your familiar method or use the [WebLogic Image Tool (WIT)](https://github.com/oracle/weblogic-image-tool).
@@ -310,7 +310,6 @@ The following configuration example illustrates a basic configuration.
 
 #### Basic configuration
 
-This example specifies the required image parameter for the domain creation image(s); all other fields are at default values.
 
 ```
 spec: