Remove Derby configuration from property template plus and more doc edits

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

Author: doxiao

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

@@ -65,10 +65,10 @@ The default domain created by the script has the following characteristics:
 * No applications deployed.
 * A T3 channel.
 
-If you are running the sample from a machine that is remote to the Kubernetes cluster where the domain will be running, you need to push the new image to a registry that is local to the cluster. In this case, you need to do the following:
+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-wlst:latest`) to the target image name.
 * Run the following command to create the domain.
 
 ```

kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image/properties-template.properties

@@ -15,14 +15,3 @@ CLUSTER_TYPE=%CLUSTER_TYPE%
 JAVA_OPTIONS=%JAVA_OPTIONS%
 T3_CHANNEL_PORT=%T3_CHANNEL_PORT%
 T3_PUBLIC_ADDRESS=%T3_PUBLIC_ADDRESS%
-#Derby Data Source parameters
-dsname=DockerDS
-dsdbname=DerbyDB;create=true
-dsjndiname=/DockerDS
-dsdriver=org.apache.derby.jdbc.ClientXADataSource
-dsurl=jdbc:derby://localhost:1527/DerbyDB;ServerName=localhost;databaseName=DerbyDB;create=true
-dsusername=dbuser
-dspassword=dbpassword
-dstestquery=SQL SELECT 1 FROM SYS.SYSTABLES
-dsinitalcapacity=0
-dsmaxcapacity=15

site/quickstart.md

@@ -177,15 +177,16 @@ respectively, as shown in the example.  If you specify the `-e` option, the scri
 Kubernetes YAML files *and* apply them to your cluster.  If you omit the `-e` option, the 
 script will just generate the YAML files, but will not take any action on your cluster.
 
-If you are running the sample from a machine that is remote to the Kubernetes cluster where the domain will be running, you need to push the new image to a registry that is local to the cluster. In this case, you need to do the following:
+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-wdti: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-wlst:latest`) to the target image name.
 * Run the following command to create the domain.
 
 ```
-kubectl create -f /some/output/directory/weblogic-domains/sample-domain1/domain.yaml
+kubectl apply -f /some/output/directory/weblogic-domains/sample-domain1/domain.yaml
 ```
+
 c.	Confirm that the operator started the servers for the domain:
 * Use `kubectl` to show that the domain resource was created:
 ```