re-apply edits

Author: rosemarymarano

README.md

@@ -3,8 +3,8 @@ WebLogic Monitoring Exporter
 
 [![Build Status](https://travis-ci.org/oracle/weblogic-monitoring-exporter.svg?branch=master)](https://travis-ci.org/oracle/weblogic-monitoring-exporter)
 
-The WebLogic Monitoring Exporter uses the [WLS RESTful Management API](https://docs.oracle.com/middleware/1221/wls/WLRUR/overview.htm#WLRUR111) to scrape runtime information, and then exports [Prometheus](http://prometheus.io)-compatible metrics.
-It is deployed as a web application in a WebLogic Server (WLS) instance, version 12.2.1 or higher, typically, in the instance from which you want to get metrics.
+The WebLogic Monitoring Exporter uses the [WLS RESTful Management API](https://docs.oracle.com/middleware/1221/wls/WLRUR/overview.htm#WLRUR111) to scrape runtime information and then exports [Prometheus](http://prometheus.io)-compatible metrics.
+It is deployed as a web application in a WebLogic Server (WLS) instance, version 12.2.1 or later, typically, in the instance from which you want to get metrics.
 
 ## Building
 
@@ -38,7 +38,7 @@ queries:
         key: servletName
         values: invocationTotalCount
 ```
-Note that there are two parts to the configuration. The optional top portion defines general processing rules:
+Note that there are two parts to the configuration. The optional top portion defines general processing rules.
 
 | Name | Description |
 | --- | --- |
@@ -56,7 +56,7 @@ Within each section, there are a number of options:
 | --- | --- |
 | `key` | The name of the attribute to use as a key for qualifiers in the output. |
 | `keyName` | The name to use for the key in the qualifier; defaults to the name of the attribute. |
-| `prefix` | A prefix to use for all metrics gathered from the current level. |
+| `prefix` | A prefix to use for all the metrics gathered from the current level. |
 | `values` | The attributes for which metrics are to be output. If not specified and a prefix is defined, all values on the MBean will be selected. |
 | `type` | A filter for subtypes. If specified, only those objects whose `type` attribute matches will be collected. |
 

samples/kubernetes/deployments/README.md

@@ -7,7 +7,7 @@ All the examples are configured to be deployed in the `monitoring` namespace. Th
 
 You can customize the examples to reflect a specific configuration.
 
-For more details on how to set up and run Prometheus and Kibana with the WebLogic Monitoring Exporter, see the blog post, [Using Prometheus and Grafana to Monitor WebLogic Server on Kubernetes](https://blogs.oracle.com/weblogicserver/use-prometheus-and-grafana-to-monitor-weblogic-server-on-kubernetes).
+For more details on how to set up and run Prometheus and Kibana with the WebLogic Monitoring Exporter, see the blog, [Using Prometheus and Grafana to Monitor WebLogic Server on Kubernetes](https://blogs.oracle.com/weblogicserver/use-prometheus-and-grafana-to-monitor-weblogic-server-on-kubernetes).
 
 
 ## Copyright

samples/kubernetes/end2end/README.md

@@ -1,5 +1,5 @@
 ## Monitoring WebLogic Server with the Grafana Dashboard
-This is an end-to-end sample that shows you the steps to set up monitoring for WebLogic domains using Prometheus and Grafana from scratch. In the end, you'll have Prometheus, Grafana, and WLS domains installed, configured, and running. This sample includes Grafana dashboards to visualize the WebLogic Server runtime metrics.
+This is an end-to-end sample that shows you the steps to set up monitoring for WebLogic domains using Prometheus and Grafana. In the end, you'll have Prometheus, Grafana, and WLS domains installed, configured, and running. This sample includes Grafana dashboards to visualize the WebLogic Server runtime metrics.
 
 First, let's look at [what's in the WebLogic Server Dashboard](docs/dashboard.md).
 
@@ -9,7 +9,7 @@ Before going into the detailed steps, look at the diagram below for the overall
 
 Here's how the WebLogic metrics come from WebLogic Server and get displayed in the dashboard:
 - WebLogic Servers expose their runtime data via the REST API.
-- The exporter, running on each WebLogic Server, acquires WebLogic data by calling the REST API, which it then translates to the Prometheus metrics format and exposes in an HTTP endpoint.
+- The exporter, running on each WebLogic Server instance, acquires WebLogic data by calling the REST API, which it then translates to the Prometheus metrics format and exposes in an HTTP endpoint.
 - The Prometheus server is responsible for periodically scraping the metrics from the endpoints and storing them in its time series database.
 - The Grafana server queries the metrics from Prometheus using PromQL and displays the metrics and series in a visualization dashboard.
 

samples/kubernetes/end2end/docs/01-pv-path.md

@@ -1,10 +1,10 @@
 ## Configuring the PV Path
-In this sample we need to create three Persistent Volumes (PV) and Persistent Volume Claims (PVC) to store data for MySQL, Prometheus, and Grafana. See the YAML files for the three PVs/PVCs.
+In this sample, we need to create three Persistent Volumes (PV) and Persistent Volume Claims (PVC) to store data for MySQL, Prometheus, and Grafana. See the YAML files for the three PVs/PVCs.
 - [PV and PVC for MYSQL server](../mysql/persistence.yaml).
 - [PV and PVC for Prometheus server](../prometheus/persistence.yaml).
 - [PV and PVC for Grafana server](../grafana/persistence.yaml).
 
-> **Note**: To simply the configuration, we use `hostPath` PV that can only work in a single-node Kubernetes cluster so it's for demonstration purposes only. In a production environment, you would need to use a more sophisticated PV type like NFS, iSCSI. For more details, see the Kubernetes [Types of Persistent Volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#types-of-persistent-volumes) document.  
+> **Note**: To simply the configuration, we use `hostPath` PV that can only work in a single-node Kubernetes cluster, therefore, it's for demonstration purposes only. In a production environment, you would need to use a more sophisticated PV type like NFS, iSCSI. For more details, see the Kubernetes [Types of Persistent Volumes](https://kubernetes.io/docs/concepts/storage/persistent-volumes/#types-of-persistent-volumes) document.  
 
 To simplify configuration and management, the three PVs will share the same root path. Prepare a host folder as the root path of the PVs.
 

samples/kubernetes/end2end/docs/02-mysql.md

@@ -21,7 +21,7 @@ kubectl get pod -l app=mysql
 NAME                    READY   STATUS    RESTARTS   AGE
 mysql-7bf4d88f9-sbd25   1/1     Running   0          31h
 ```
-Get pod name of MySQL server.
+Get the pod name of MySQL server.
 ```
 POD_NAME=$(kubectl get pod -l app=mysql -o jsonpath="{.items[0].metadata.name}")
 ```

samples/kubernetes/end2end/docs/03-wls-operator.md

@@ -8,7 +8,7 @@ Pull the WLS Kubernetes Operator 2.1 image.
 docker pull oracle/weblogic-kubernetes-operator:2.1
 ```
 Pull the WebLogic 12.2.1.3 image from the Oracle Container Registry site.
-First, you need a valid user name and password to log in to the site. For details, see [here](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-domains/domain-in-image/base-images/_index.md#obtaining-standard-images-from-the-oracle-container-registry).
+First, you need a valid user name and password to log in to the site. For details, see [here](https://oracle.github.io/weblogic-kubernetes-operator/userguide/managing-domains/domain-in-image/base-images/#obtaining-standard-images-from-the-oracle-container-registry).
 ```
 docker login container-registry.oracle.com
 docker pull container-registry.oracle.com/middleware/weblogic:12.2.1.3

samples/kubernetes/end2end/docs/05-prometheus.md

@@ -41,7 +41,7 @@ prometheus-server               NodePort    10.99.199.236   <none>        80:300
 ```
 ### Access the Prometheus web UI
 Now you can access the Prometheus web UI in your browser with the URL `http://<HostIP>:30000`.  
-In the top menu, click `Status` and then `Targets`. The target page is displayed. Go to the bottom of the page. You'll find the two endpoints of `wls-domain1` are up and healthy.
+In the top menu, click `Status` and then `Targets`. The target page is displayed. Go to the bottom of the page. You'll find that the two endpoints of `wls-domain1` are up and healthy.
 
 ![Prometheus Targets](./images/prometheus-targets.png)
 

samples/kubernetes/end2end/docs/dashboard.md

@@ -2,7 +2,7 @@
 ### Overview
 The WebLogic Server Grafana dashboard provides a visualization of WebLogic Server runtime metrics allowing you to monitor and diagnose the runtime deployment of WebLogic Server.
 
-At the top, left-hand corner of the dashboard page, there are filters which let you filter out metrics based on different domains, different clusters, and different servers. Another filter is the `Top N` whose candidates values are 3, 5, 7, and 10. The value will be applied to some panels to show only the top N elements, to avoid too many elements being displayed.  
+At the top, left-hand corner of the dashboard page, there are filters which let you filter out metrics based on different domains, different clusters, and different servers. Another filter is the `Top N` whose candidate values are 3, 5, 7, and 10. The value will be applied to panels to show only the top N elements, thus avoiding too many elements being displayed.  
 
 The WebLogic Server dashboard has four rows: `Servers`, `Web Applications`, `Data Sources` and `JMS Services`. Each row can be folded and unfolded separately.