additional edits

Author: rosemarymarano

site/quickstart.md

@@ -4,12 +4,12 @@ Use this quick start guide to create a WebLogic deployment in a Kubernetes clust
 These instructions assume that you are already familiar with Kubernetes.  If you need more detailed instructions, please
 refer to the [User guide](user-guide.md).
 
-> If you have an old version of the operator installed on your cluster you must remove
-  it before installing this version.  You should remove the deployment (for example `kubectl delete deploy weblogic-operator -n your-namespace`) and the custom
-  resource definition (for example `kubectl delete crd domain`).  If you do not remove
-  the custom resource definition you may see errors like this: 
-  
-    `Error from server (BadRequest): error when creating "/scratch/output/uidomain/weblogic-domains/uidomain/domain.yaml": 
+> If you have an older version of the operator installed on your cluster, you must remove
+  it before installing this version.  You should remove the deployment (for example, `kubectl delete deploy weblogic-operator -n your-namespace`) and the custom
+  resource definition (for example, `kubectl delete crd domain`).  If you do not remove
+  the custom resource definition you may see errors like this:
+
+    `Error from server (BadRequest): error when creating "/scratch/output/uidomain/weblogic-domains/uidomain/domain.yaml":
     the API version in the data (weblogic.oracle/v2) does not match the expected API version (weblogic.oracle/v1`
 
 ## Prerequisites
@@ -32,7 +32,7 @@ b.  Log in to the Docker Store from your docker client:
 ```
 $ docker login
 ```
-c.	Pull the operator image and tag it to the default image value of the operator:
+c.	Pull the operator image and tag it with the default image value of the operator:
 ```
 $ docker pull oracle/weblogic-kubernetes-operator:2.0-rc1
 $ docker tag oracle/weblogic-kubernetes-operator:2.0-rc1 weblogic-kubernetes-operator:2.0
@@ -170,9 +170,9 @@ $ cd kubernetes/samples/scripts/create-weblogic-domain/domain-home-in-image
 $ ./create-domain.sh -i my-inputs.yaml -o /some/output/directory -u username -p password -e
 ```
 
-You need to provide the WebLogic administration username and password in the `-u` and `-p` options
-respectively, as shown in the example.  If you specify the `-e` option, the script will generate the 
-Kubernetes YAML files *and* apply them to your cluster.  If you omit the `-e` option, the 
+You need to provide the WebLogic administration user name and password in the `-u` and `-p` options
+respectively, as shown in the example.  If you specify the `-e` option, the script will generate the
+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.
 
 c.	Confirm that the operator started the servers for the domain:
@@ -201,9 +201,9 @@ $ helm install kubernetes/samples/charts/ingress-per-domain \
   --set traefik.hostname=sample-domain1.org
 ```
 
-e.	To confirm that the load balancer noticed the new Ingress and is successfully routing to the domain's server pods
-    you can hit the URL for the "WebLogic Ready App" which will return a HTTP 200 status code as
-    shown in the example below.  If you used the host-based routing ingress sample you will need to
+e.	To confirm that the load balancer noticed the new Ingress and is successfully routing to the domain's server pods,
+    you can hit the URL for the "WebLogic Ready App" which will return a HTTP 200 status code, as
+    shown in the example below.  If you used the host-based routing Ingress sample, you will need to
     provide the hostname in the `-H` option:
 ```
 $ curl -v -H 'host: sample-domain1.org' http://your.server.com:30305/weblogic/

@@ -234,7 +234,7 @@ b.	Remove the domain resources by using the sample [`delete-weblogic-domain-reso
 ```
 $ kubernetes/samples/scripts/delete-domain/delete-weblogic-domain-resources.sh -d sample-domain1
 ```
-c.	Use `kubectl` to confirm that the server pods and domain resource are gone.
+c.	Use `kubectl` to confirm that the server pods and domain resource are gone:
 ```
 $ kubectl get pods -n sample-domain1-ns
 $ kubectl get domains -n sample-domain1-ns
@@ -252,7 +252,7 @@ $ helm upgrade \
   stable/traefik
 ```
 
-b.	Configure the operator to stop managing the domain.
+b.	Configure the operator to stop managing the domain:
 
 ```
 $ helm upgrade \