Reveiw Feedback Incorporated

Author: Ashish Chalak

docs-source/content/wcsites-domains/manage-wcsites-domains/WebLogic-Monitoring-Exporter-Setup.md

@@ -255,9 +255,9 @@ To deploy the service monitor, use the above wls-exporter.yaml deployment YAML a
 $ kubectl create -f kubernetes/samples/scripts/create-wcsites-domain/utils/weblogic-monitoring-exporter/wls-exporter.yaml
 ```
 
-#### Additional Setup For LoadBalancer Voyager
+#### Additional Setup For Load Balancer Voyager
 
-In step 2 of [Configure voyager to manage ingresses]({{< relref "/wcsites-domains/manage-wcsites-domains/loadbalancer-voyager-setup-for-wcsites-domain-setup-on-k8s#configure-voyager-to-manage-ingresses">}}), for wcsites-cluster, enable the last rule for path ‘wls-exporter’ and then redeploy voyager LoadBalancer.
+In step 2 of [Configure Voyager to Manage Ingresses]({{< relref "/wcsites-domains/manage-wcsites-domains/loadbalancer-voyager-setup-for-wcsites-domain-setup-on-k8s#configure-voyager-to-manage-ingresses">}}), for wcsites-cluster, enable the last rule for path ‘wls-exporter’ and then re-deploy Voyager Load Balancer.
 
 #### Enable Prometheus to Discover the Service
 

docs-source/content/wcsites-domains/pre-requisites/_index.md

@@ -48,7 +48,7 @@ following limitations currently exist for WebCenter Sites domain:
 * We do not currently support running WebCenter Sites in non-Linux containers.
 * Deploying and running a WebCenter Sites domain is supported only in Operator versions 2.4.0 and later.
 * The [WebLogic Logging Exporter](https://github.com/oracle/weblogic-logging-exporter)
-  currently supports WebLogic Server logs only.  Other logs will not be sent to Elasticsearch.  Note, however, that you can use a sidecar with a log handling tool like Logstash or fluentd to get logs.
+  currently supports WebLogic Server logs only.  Other logs will not be sent to Elasticsearch.  Note, however, that you can use a sidecar with a log handling tool like Logstash or Fluentd to get logs.
 * The [WebLogic Monitoring Exporter](https://github.com/oracle/weblogic-monitoring-exporter)
   currently supports the WebLogic MBean trees only.  Support for JRF MBeans has not been added yet.
 

docs-source/content/wcsites-domains/prepare-your-environment/_index.md

@@ -29,7 +29,6 @@ After creating Kubernetes clusters, you can optionally:
 * Create load balancers to direct traffic to backend domains.
 * Configure Kibana and Elasticsearch for your operator logs.
 
-
 #### Build Oracle WebCenter Sites Image
 
 Build Oracle WebCenter Sites 12.2.1.4.0 Image by following steps 4A, 4C, 4D and 5 from this [document](https://github.com/oracle/docker-images/tree/master/OracleWebCenterSites/dockerfiles/12.2.1.4).
@@ -263,7 +262,7 @@ $ cd <work directory>/weblogic-kubernetes-operator-2.4.0
 	{"timestamp":"03-14-2020T06:49:57.910+0000","thread":21,"fiber":"fiber-1","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.rest.RestServer","method":"start","timeInMillis":1584168597910,"message":"Started the internal ssl REST server on https://0.0.0.0:8082/operator","exception":"","code":"","headers":{},"body":""}	{"timestamp":"03-14-2020T06:49:57.913+0000","thread":21,"fiber":"fiber-1","domainUID":"","level":"INFO","class":"oracle.kubernetes.operator.Main","method":"markReadyAndStartLivenessThread","timeInMillis":1584168597913,"message":"Starting Operator Liveness Thread","exception":"","code":"","headers":{},"body":""}
     ```
 
-#### Configure NFS(Network File System) Server
+#### Configure NFS (Network File System) Server
 To configure NFS server, install the nfs-utils package preferably on Master node:
 
 ```bash
@@ -284,7 +283,9 @@ $ sudo mkdir -p /scratch/K8SVolume
 $ sudo chown -R 1000:1000 /scratch/K8SVolume
 ```
 
-Note: NFS Server host name or IP address and NFS Share path which is used when you create PV/PVC in further sections.
+host name or IP address of the NFS Server
+
+Note: Host name or IP address of the NFS Server and NFS Share path which is used when you create PV/PVC in further sections.
 
 #### Prepare the Environment for the WebCenter Sites Domain
 1. Unless you would like to use the default namespace, create a Kubernetes namespace that can host one or more domains: