more cleanup and edits

Author: rosemarymarano

documentation/staging/content/_index.md

@@ -30,7 +30,7 @@ For detailed user information, read the following:
     - [Kubernetes]({{< relref "/navigate/kubernetes/_index.md" >}})
     - [Verrazzano]({{< relref "/navigate/verrazzano.md" >}})
 
-For developer information, see [WebLogic Kubernetes Toolkit UI Project]({{< relref "/developer/_index.md" >}})
+For developer information, see [WebLogic Kubernetes Toolkit UI Project]({{< relref "/developer/_index.md" >}}).
 
 ### Get Help
 

documentation/staging/content/navigate/image.md

@@ -15,8 +15,8 @@ weight: 3
     - [WebLogic Deploy Tooling Configuration](#weblogic-deploy-tooling-configuration)
     - [Image Build Configuration](#image-build-configuration)
 - [Code View](#code-view)
-- [Create Image](#create-image)
-- [Push Image](#push-image)
+- [Create Images](#create-images)
+- [Push Images](#push-images)
 
 ### Image
 The `Image` section helps you build container images for deploying WebLogic-based applications
@@ -33,9 +33,10 @@ Auxiliary images are available for the "Model in Image" [domain location]({{< re
 One primary image can be reused for hundreds of domains whereas an auxiliary image is domain-specific. When using auxiliary images,
 the primary image contains the OS, JDK, and FMW software installations; the auxiliary image supplies the specifics for a single domain.
 
-Use the `Design View` to create a new or use an existing (the default) `Primary Image` and, for Model in Image domains only, an `Auxiliary Image`.
-The `Design View` page for the `Primary Image` and the `Auxiliary Image` has several panes and a few advanced panes.
-Note that _not all_ the fields described for the `Primary Image` are relevant for an `Auxiliary Image`, such as the JDK and Oracle installers, and patching. The exceptions are noted.
+Use the `Design View` page to create a new or use an existing (the default) `Primary Image` and,
+for "Model in Image" domains only, create a new (the default) or use an existing `Auxiliary Image`.
+The `Design View` page has the following basic panes and a few advanced panes.
+Note that _not all_ the fields described for the `Primary Image` are relevant for an `Auxiliary Image`. The exceptions are noted.
 
 - [Target Image Name and Registry Credentials](#target-image-name-and-registry-credentials)
 - [Base Image to Use](#base-image-to-use)
@@ -143,7 +144,7 @@ as secure as possible, this really should be a last resort._
 #### WebLogic Deploy Tooling Configuration
 This `Advanced` pane applies only to images using either the "Model in Image" or "Domain in Image" [domain locations]({{< relref "/navigate/project-settings#choosing-a-domain-location" >}}).
 
-For "Domain in Image" only, the `Domain Type` field tells WebLogic Deploy Tooling what type of domain to create and you use the `Domain Home Directory`
+For "Domain in Image" only, the `Domain Type` field tells WebLogic Deploy Tooling what type of domain to create. Use the `Domain Home Directory`
 to change the location of the WebLogic domain directory inside the container.  For "Model in Image" and "Domain in Image", the `Model Home Directory` field
 specifies the directory where the WDT model files are stored in the image and `WDT Home Directory` specifies the WDT home directory inside the image.
 Typically, there is no need to override these directory locations because the application defaults follow the recommended best practices.
@@ -192,7 +193,7 @@ set environment variables to specify any credentials required by the script to e
 the script itself.  This change is left as an exercise for you because different environments typically will have
 existing standards for securely handling such credentials.
 
-### Create Primary Image and Create Auxiliary Image
+### Create Images
 The `Create Primary Image` and `Create Auxiliary Image` actions invoke the [WebLogic Image Tool](https://oracle.github.io/weblogic-image-tool/) to
 create a new container image for running a WebLogic domain in a Kubernetes environment.  You can access these actions using
 the `Create Primary Image` or `Create Auxiliary Image` button on the `Image` page or from the `Go` menu.
@@ -206,7 +207,7 @@ At a high level, the action performs the following steps:
 4. Builds the image on the local machine using the WebLogic Image Tool
    [Create](https://oracle.github.io/weblogic-image-tool/userguide/tools/create-image/) command.
 
-### Push Primary Image and Push Auxiliary Image
+### Push Images
 The `Push Primary Image` and `Push Auxiliary Image` actions use the specified Image Builder program to upload (that is, push) the newly-built image
 to the image registry specified by its image tag.  You can access these actions by using the `Push Primary Image` or `Push Auxiliary Image` button on the `Image`
 page or from the `Go` menu.

documentation/staging/content/navigate/kubernetes/k8s-wko.md

@@ -164,11 +164,11 @@ the script itself.  This change is left as an exercise for you because different
 existing standards for securely handling such credentials.
 
 ### Install Operator
-`Push Image` uses the specified Image Builder program to upload (that is, push) the newly-built image
-to the image registry specified by its image tag.  You can access it by using the `Install Operator` button on the
+The `Install Operator` action installs the WebLogic Kubernetes Operator in the target Kubernetes cluster. 
+You can access it by using the `Install Operator` button on the
 `WebLogic Operator` page or `Go` > `Install WebLogic Kubernetes Operator`.
 
-At a high level, `Push Image` performs the following steps:
+At a high level, `Install Operator` performs the following steps:
 
 1. Validates the input values necessary for running the action based on your selections.
 2. Saves the WKT Project, if needed.

documentation/staging/content/navigate/model.md

@@ -157,7 +157,7 @@ In replacing credential values, `Prepare Model` must handle the replacement diff
 
 - With "Domain in Image", the WebLogic Image Tool creates the domain while creating the image.  As such, it has no
 knowledge of Kubernetes so the token replacement uses variable tokens so that domain creation has access to the actual
-credential values.  You must ensure that all variables have valid values prior to running `Create Image`.
+credential values.  You must ensure that all variables have valid values prior to running `Create Primary Image`.
 
 - For "Model in Image", the domain is created at runtime by the WebLogic Kubernetes Operator running in a Kubernetes
 cluster.  As such, token replacement uses secret tokens for all credential fields.  You must to be sure to provide

documentation/staging/content/release notes/_index.md

@@ -9,7 +9,7 @@ pre = "<b> </b>"
 
 - When running the WKT UI application on Windows, the image builder tool (docker or podman) also must be directly executable in Windows.  For example, there is currently no support for running the WKT UI application in Windows and running podman under the Windows Subsystem for Linux (WSL2).  However, running Docker Desktop for Windows with a WSL2 backend _is_ fully supported because the `docker` command is executable directly in Windows (without having to call WSL2). If you need to use podman on Windows, then refer to the podman blog entries at https://podman.io/blogs/2021/09/06/podman-on-macs.html and https://podman.io/blogs/2020/09/02/running_windows_or_mac.html for more information about downloading, installing, and configuring the Windows Remote Client.
 
-- On Linux, the application depends on libGL being installed.  libGL is not currently listed in the dependencies list for the rpm (or deb) installers.  Therefore, you will need to install libGL using your package manager.  For example:
+- On Linux, the application depends on libGL being installed.  libGL is not currently listed in the dependencies list for the `rpm` (or `deb`) installers.  Therefore, you will need to install libGL using your package manager.  For example:
   ```
 	sudo yum install libGL
   ```