Minor update to doc

Signed-off-by: doxiao <[email protected]>

Author: doxiao

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

@@ -68,7 +68,7 @@ The default domain created by the script has the following characteristics:
 If you run the sample from a machine that is remote to the Kubernetes cluster, and you need to push the new image to a registry that is local to the cluster, you need to do the following:
 * Set the `image` property in the inputs file to the target image name (including the tag if needed).
 * Run the `create-domain.sh` script without the `-e` option.
-* Push the generated image `domain-home-in-image-wdt:lastest` (or `domain-home-in-image-wlst:latest`) to the target image name.
+* Push the generated image `domain-home-in-image-wdt:lastest` (or `domain-home-in-image:latest`) to the target image name.
 * Run the following command to create the domain.
 
 ```
@@ -93,7 +93,7 @@ The following parameters can be provided in the inputs file.
 | `domainUID` | Unique ID that will be used to identify this particular domain. Used as the name of the generated WebLogic domain as well as the name of the Kubernetes domain resource. This ID must be unique across all domains in a Kubernetes cluster. This ID cannot contain any character that is not valid in a Kubernetes service name. | `domain1` |
 | `exposeAdminNodePort` | Boolean indicating if the Administration Server is exposed outside of the Kubernetes cluster. | `false` |
 | `exposeAdminT3Channel` | Boolean indicating if the T3 administrative channel is exposed outside the Kubernetes cluster. | `false` |
-| `image` | WebLogic Docker image that the domain resource will pull if needed. You only need to specify this if you are going to tag the generated image to a different name. If not specified, the sample uses the internally generated image name, either "domain-home-in-image-wdt:latest" or "domain-home-in-image-wlst:latest". | |
+| `image` | WebLogic Docker image that the domain resource will pull if needed. You only need to specify this if you are going to tag the generated image to a different name. If not specified, the sample uses the internally generated image name, either "domain-home-in-image-wdt:latest" or "domain-home-in-image:latest". | |
 | `imagePullPolicy` | WebLogic Docker image pull policy. Legal values are "IfNotPresent", "Always", or "Never" | `IfNotPresent` |
 | `imagePullSecretName` | Name of the Kubernetes secret to access the Docker Store to pull the WebLogic Server Docker image. The presence of the secret will be validated when this parameter is specified |  |
 | `includeServerOutInPodLog` | Boolean indicating whether to include server .out to the pod's stdout. | `true` |

site/quickstart.md

@@ -180,7 +180,7 @@ script will just generate the YAML files, but will not take any action on your c
 If you run the sample from a machine that is remote to the Kubernetes cluster, and you need to push the new image to a registry that is local to the cluster, you need to do the following:
 * Set the `image` property in the inputs file to the target image name (including the tag if needed).
 * Run the `create-domain.sh` script without the `-e` option.
-* Push the generated image `domain-home-in-image-wdt:lastest` (or `domain-home-in-image-wlst:latest`) to the target image name.
+* Push the generated image `domain-home-in-image-wdt:lastest` (or `domain-home-in-image:latest`) to the target image name.
 * Run the following command to create the domain.
 
 ```