edits from Tom B

Author: rosemarymarano

site/README.md

@@ -1,8 +1,10 @@
-# Oracle WebLogic Server Kubernetes Operator Documentation
+# Oracle WebLogic Server Kubernetes Operator documentation
 
-This directory contains the documentation for the current version of the operator, version 2.0. 
+This directory contains the documentation for the current version of the operator, version 2.0.
 
-If you wish to view documentation for an older version please see:
+If you wish to view documentation for an older version, please see:
 
 * [Version 1.0](v1.0)
-* [Version 1.1](v1.1)
+* [Version 1.1](v1.1)
+
+For a guide to the operator project, refer to this [README](../README.md).

site/creating-domain.md

@@ -2,12 +2,14 @@
 
 The WebLogic domain must be installed into the folder that will be mounted as `/shared/domain`. The recommended approach is to use the provided `create-weblogic-domain.sh` script; however, instructions are also provided for manually installing and configuring a WebLogic domain (see [Manually creating a domain](manually-creating-domain.md)).
 
+In this version of the operator, a WebLogic domain can be located either in a persistent volume (PV) or in a Docker image. To learn more about both approaches, see [Create and manage WebLogic domains](domains.md). For examples of each, see the [WebLogic operator samples](../kubernetes/samples/README.md).
+
 ## Important considerations and restrictions for WebLogic domains in Kubernetes
 
 When running a WebLogic domain in Kubernetes, there are some additional considerations that must be taken into account to ensure correct functioning:
 
 *	Multicast is not currently well supported in Kubernetes.  Some networking providers have some support for multicast, but it is generally considered of “beta” quality.  Oracle recommends configuring WebLogic clusters to use unicast.
-*	The `ListenAddress` for all servers must be set to the correct DNS name; it should not be set to `0.0.0.0` or left blank.  This is required for cluster discovery of servers to work correctly.
+*	The `ListenAddress` for all servers must be set to the correct DNS name or left blank.  This is required for cluster discovery of servers to work correctly.
 *	If there is a desire to expose a T3 channel outside of the Kubernetes cluster -- for example, to allow WLST or RMI connections from clients outside Kubernetes -- then the recommended approach is to define a dedicated channel (per server) and to expose that channel using a `NodePort` service.  It is required that the channel’s internal and external ports be set to the same value as the chosen `NodePort`; for example, they could all be `32000`.  If all three are not the same, WebLogic Server will reject T3 connection requests.
 
 ## Creating a domain namespace
@@ -147,8 +149,8 @@ $ ./create-weblogic-domain.sh -e -v \
   -o /path/to/weblogic-operator-output-directory
 ```
 
-The `-e` option tells the script that it should not only create the YAML files but also apply them to the Kubernetes environment. 
-If you omit this option, the YAML files will be generated in the output directory and you can inspect them and apply them manually. 
+The `-e` option tells the script that it should not only create the YAML files but also apply them to the Kubernetes environment.
+If you omit this option, the YAML files will be generated in the output directory and you can inspect them and apply them manually.
 
 ## What the script does
 

site/quickstart.md

@@ -7,6 +7,8 @@ refer to the [User guide](user-guide.md).
 ## Prerequisites
 For this exercise, you’ll need a Kubernetes cluster. If you need help setting one up, check out our [cheat sheet](k8s_setup.md).
 
+The operator uses Helm to create and deploy necessary resources and then run the operator in a Kubernetes cluster. For Helm installation and usage information, see [Using operator Helm charts](helm-charts.md).
+
 You should clone this repository to your local machine so that you have access to the
 various sample files mentioned throughout this guide:
 ```
@@ -180,27 +182,27 @@ d.	Create an Ingress for the domain, in the domain namespace, by using the [samp
 ```
 $ cd kubernetes/samples/charts
 $ helm install ingress-per-domain --name domain1-ingress --values ingress-per-domain/values.yaml
-``` 
+```
 
 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 
+    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: domain1.org' http://your.server.com:30305/weblogic/

-* 
About to connect() to your.server.com port 30305 (#0)

+*
About to connect() to your.server.com port 30305 (#0)

 *   Trying 10.196.1.64...

 * Connected to your.server.com (10.196.1.64) port 30305 (#0)
 
> GET /weblogic/ HTTP/1.1

 > User-Agent: curl/7.29.0

 > Accept: */*

 > host: domain1.org

-> 
+>
 
< HTTP/1.1 200 OK

 < Content-Length: 0

 < Date: Thu, 20 Dec 2018 14:52:22 GMT
 
< Vary: Accept-Encoding

-< 
* Connection #0 to host your.server.com left intact

+<
* Connection #0 to host your.server.com left intact

 ```
 **Note**: Depending on where your Kubernetes cluster is running, you may need to open firewall ports or
 update security lists to allow ingress to this port.