Minor changes to the samples documentation for the Model in Image and Domain on PV.

Author: ankedia

documentation/4.1/content/samples/domains/domain-home-on-pv/_index.md

@@ -12,11 +12,15 @@ description: "Sample for creating a WebLogic domain home on a persistent volume
 This sample demonstrates deploying a
 [Domain on PV]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}) domain home source type
  with [Domain creation images]({{< relref "/managing-domains/domain-on-pv/domain-creation-images.md" >}}).
-The Domain on PV sample uses a WebLogic Deploy Tooling (WDT) model to specify your initial WebLogic configuration. For more information about WDT models, see [Working with model files]({{<relref "/managing-domains/working-with-wdt-models/model-files.md" >}}) in the user documentation.
+The Domain on PV sample uses a WebLogic Deploy Tooling (WDT) model to specify your initial WebLogic configuration. 
+
+WDT models are a convenient and simple alternative to WebLogic Scripting Tool (WLST) configuration scripts and templates. They compactly define a WebLogic domain using model files, variable properties files, and application archives files. The WDT model format is described in the open source, [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) GitHub project, and the required directory structure for a WDT archive is specifically discussed [here](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/).
+
+For more information on Domain on PV, see the [Domain on PV]({{< relref "/managing-domains/domain-on-pv/_index.md" >}}) user documentation. 
 
 #### Domain on PV domain types (WLS and JRF)
 
-Domain on PV is supported on two types of domains: a standard Oracle WebLogic Server domain and an Oracle Fusion Middleware Infrastructure, Java Required Files (JRF) domain. This sample demonstrates both Oracle WebLogic Server (WLS) and JRF domain types.
+Domain on PV is supported on two types of domains: a standard Oracle WebLogic Server (WLS) domain and an Oracle Fusion Middleware Infrastructure, Java Required Files (JRF) domain. This sample demonstrates both Oracle WebLogic Server (WLS) and JRF domain types.
 
 The JRF domain path through the sample includes additional steps required for JRF: deploying an infrastructure database, initializing the database using the Repository Creation Utility (RCU) tool, referencing the infrastructure database from the WebLogic configuration, setting an Oracle Platform Security Services (OPSS) wallet password, and exporting or importing an OPSS wallet file. JRF domains may be used by Oracle products that layer on top of WebLogic Server, such as SOA and OSB.
 

documentation/4.1/content/samples/domains/domain-home-on-pv/build-domain-creation-image.md

@@ -124,7 +124,7 @@ The archive top directory, named `wlsdeploy`, contains a directory named `applic
 ```
 {{% /expand %}}
 
-The application displays important details about the WebLogic Server instance that it's running on: namely its domain name, cluster name, and server name, as well as the names of any data sources that are targeted to the server. Also, you can see that application output reports that it's at version `v1`; you will update this to `v2` in a later use case that demonstrates upgrading the application.
+The application displays important details about the WebLogic Server instance that it's running on: namely its domain name, cluster name, and server name, as well as the names of any data sources that are targeted to the server. Also, you can see that application output reports that it's at version `v1`.
 
 #### Stage a ZIP file of the archive
 
@@ -316,7 +316,7 @@ Run the following commands to create the image and verify that it worked:
 
 If you don't see the `imagetool` directory, then you missed a step in the [prerequisites]({{< relref "/samples/domains/domain-home-on-pv/prerequisites.md" >}}).
 
-This command runs the WebLogic Image Tool to create the image and does the following:
+This command runs the WebLogic Image Tool to create the domain creation image and does the following:
 
   - Builds the final container image as a layer on a small `busybox` base image.
   - Copies the WDT ZIP file that's referenced in the WIT cache into the image.

documentation/4.1/content/samples/domains/domain-home-on-pv/cleanup.md

@@ -53,12 +53,6 @@ weight: 4
         --set "kubernetes.namespaces={traefik}"
     ```
 
-1.	Delete the domain namespace.
-
-    ```shell
-    $ kubectl delete namespace sample-domain1-ns
-    ```
-
 #### Remove the operator
 
 1.	Remove the operator.

documentation/4.1/content/samples/domains/domain-home-on-pv/sample.md

@@ -11,10 +11,7 @@ description: "Sample for creating a WebLogic domain home on a PV for deploying t
 
 The sample demonstrates setting up a WebLogic domain with a domain home on a Kubernetes PersistentVolume (PV) (Domain on PV). This involves:
 
-  - Building a [domain creation image](#domain-creation-image) with:
-    - A WDT model that describes your WebLogic domain configuration.
-    - A WDT archive ZIP file that contains your applications.
-    - A WDT installation that contains the binaries for running WDT.
+  - Using the [domain creation image](#domain-creation-image) that you previously built.
   - Creating secrets for the domain.
   - Creating a Domain resource YAML file for the domain that:
     - References your Secrets and a WebLogic image.
@@ -343,7 +340,7 @@ Events:
 ```
 {{% /expand %}}
 
-In the `Status` section of the output, the available servers and clusters are listed.  Note that if this command is issued very soon after the script finishes, there may be no servers available yet, or perhaps only the Administration Server but no Managed Servers.  The operator will start up the Administration Server first and wait for it to become ready before starting the Managed Servers.
+In the `Status` section of the output, the available servers and clusters are listed.  Note that if this command is issued very soon after the domain resource is applied, there may be no servers available yet, or perhaps only the Administration Server but no Managed Servers.  The operator will start up the Administration Server first and wait for it to become ready before starting the Managed Servers.
 
 ### Verify the pods
 
@@ -499,3 +496,7 @@ If the PVC and PV were created by the operator and you don't want to preserve th
 $ kubectl delete PVC sample-domain1-weblogic-sample-pvc -n sample-domain1-ns
 $ kubectl delete PV sample-domain1-weblogic-sample-pv
 ```
+
+#### Delete the domain namespace.
+
+$ kubectl delete namespace sample-domain1-ns

documentation/4.1/content/samples/domains/model-in-image/_index.md

@@ -11,14 +11,14 @@ description: "Sample for supplying a WebLogic Deploy Tooling (WDT) model that th
 
 This sample demonstrates deploying a [Model in Image]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}) domain home source type
 with [Auxiliary images]({{< relref "/managing-domains/model-in-image/auxiliary-images.md" >}}).
-Unlike Domain on PV and Domain in Image, Model in Image eliminates the need to pre-create
+Model in Image eliminates the need to pre-create
 your WebLogic domain home prior to deploying your Domain YAML file.
 Instead, Model in Image uses a
 WebLogic Deploy Tooling (WDT) model to specify your WebLogic configuration.
 
-WDT models are a convenient and simple alternative to WebLogic Scripting Tool (WLST) configuration scripts and templates. They compactly define a WebLogic domain using YAML files and support including application archives in a ZIP file. The WDT model format is described in the open source, [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) GitHub project, and the required directory structure for a WDT archive is specifically discussed [here](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/).
+WDT models are a convenient and simple alternative to WebLogic Scripting Tool (WLST) configuration scripts and templates. They compactly define a WebLogic domain using model files, variable properties files, and application archives files. The WDT model format is described in the open source, [WebLogic Deploy Tooling](https://oracle.github.io/weblogic-deploy-tooling/) GitHub project, and the required directory structure for a WDT archive is specifically discussed [here](https://oracle.github.io/weblogic-deploy-tooling/concepts/archive/).
 
-Furthermore, the Model in Image auxiliary image option lets you supply your WDT artifacts
+Furthermore, the Model in Image auxiliary image option lets you supply your WDT model files
 in a small separate image separate from your WebLogic image.
 
 For more information on Model in Image, see the [Model in Image]({{< relref "/managing-domains/model-in-image/_index.md" >}}) user guide. For a comparison of Model in Image to other domain home source types, see [Choose a domain home source type]({{< relref "/managing-domains/choosing-a-model/_index.md" >}}).
@@ -29,7 +29,7 @@ This sample demonstrates five Model in Image use cases:
 
 - [Initial]({{< relref "/samples/domains/model-in-image/initial.md" >}}): An initial WebLogic domain with the following characteristics:
 
-   - Auxiliary image `model-in-image:WLS-AI-v1` with:
+   - Auxiliary image `wdt-domain-image:WLS-v1` with:
      - A WebLogic Deploy Tooling (WDT) installation
      - A WDT archive with version `v1` of an exploded Java EE web application
      - A WDT model with:
@@ -67,11 +67,11 @@ This sample demonstrates five Model in Image use cases:
 
 - [Update 3]({{< relref "/samples/domains/model-in-image/update3.md" >}}): Demonstrates deploying an updated auxiliary image with an updated application to the Update 1 use case domain and then restarting (rolling) its domain to propagate the change. Updates:
 
-  - Auxiliary image `model-in-image:WLS-AI-v2`, similar to `model-in-image:WLS-AI-v1` image with:
+  - Auxiliary image `wdt-domain-image:WLS-v2`, similar to `wdt-domain-image:WLS-v1` image with:
     - An updated web application `v2` at the `myapp-v2` directory path instead of `myapp-v1`
     - An updated model that points to the new web application path
   - Domain:
-    - Same as the Update 1 use case, except `spec.image` is `model-in-image:WLS-AI-v2`
+    - Same as the Update 1 use case, except `spec.image` is `wdt-domain-image:WLS-v2`
 
 - [Update 4]({{< relref "/samples/domains/model-in-image/update4.md" >}}): Demonstrates dynamically updating the running Update 1 or Update 3 WebLogic domain configuration without requiring a domain restart (roll). Updates:
 

documentation/4.1/content/samples/domains/model-in-image/cleanup.md

@@ -49,10 +49,10 @@ To remove the resources you have created in these samples:
 
 7. Delete the images you may have created in this sample:
    ```shell
-   $ docker image rm model-in-image:WLS-AI-v1
+   $ docker image rm wdt-domain-image:WLS-AI-v1
    ```
    ```shell
-   $ docker image rm model-in-image:WLS-AI-v2
+   $ docker image rm wdt-domain-image:WLS-AI-v2
    ```
    ```shell
    $ docker image rm model-in-image:JRF-AI-v1

documentation/4.1/content/samples/domains/model-in-image/initial.md

@@ -10,7 +10,7 @@ weight: 2
 
 In this use case, you set up an initial WebLogic domain. This involves:
 
-  - Creating an auxiliary image with:
+  - Using the [auxiliary image](#auxiliary-image) that you previously created, it contains:
     - A WDT archive ZIP file that contains your applications.
     - A WDT model that describes your WebLogic configuration.
     - A WDT installation that contains the binaries for running WDT.
@@ -31,7 +31,7 @@ The sample uses an `auxiliary image` with the name `wdt-domain-image:WLS-v1` tha
 
 ### Deploy resources - Introduction
 
-In this section, you will deploy the new image to namespace `sample-domain1-ns`, including the following steps:
+In this section, you will deploy the domain resource with the new auxliliary image to namespace `sample-domain1-ns`, including the following steps:
 
   - Create a Secret containing your WebLogic administrator user name and password.
   - Create a Secret containing your Model in Image runtime encryption password:

documentation/4.1/content/samples/domains/model-in-image/prerequisites.md

@@ -24,7 +24,7 @@ description: "Follow these prerequisite steps for WLS domain type."
 
    For additional information about obtaining the operator source, see the [Developer Guide Requirements](https://oracle.github.io/weblogic-kubernetes-operator/developerguide/requirements/).
 
-1. Copy the Model in Image sample to a new directory; for example, use directory /tmp/sample.
+1. Copy the Model in Image sample to a new directory; for example, use directory `/tmp/sample`.
    ```
    $ mkdir -p /tmp/sample
    ```