fix3

docs/guides/elasticsearch/monitoring/using-builtin-prometheus.md

@@ -119,7 +119,7 @@ prometheus.io/port: 56790
 prometheus.io/scrape: true
 ```
 
-The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from exporter.
+The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from the exporter.
 
 ## Configure Prometheus Server
 
@@ -267,7 +267,7 @@ deployment.apps/prometheus created
 
 ### Verify Monitoring Metrics
 
-Prometheus server is running on port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
 At first, let's check if the Prometheus pod is in `Running` state.
 

docs/guides/elasticsearch/monitoring/using-coreos-prometheus-operator.md

@@ -31,15 +31,15 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov
   namespace "demo" created
   ```
 
-- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you already don't have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
+- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you don't already have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
 
 - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server).
 
 > Note: YAML files used in this tutorial are stored in [docs/examples/elasticsearch](https://github.com/kubedb/cli/tree/master/docs/examples/elasticsearch) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli).
 
 ## Find out required labels for ServiceMonitor
 
-We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of Elasticsearch crd so that KubeDB creates respective `ServiceMonitor` with these labels.
+We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of Elasticsearch crd so that KubeDB creates `ServiceMonitor` object accordingly.
 
 At first, let's find out the available Prometheus server in our cluster.
 
@@ -222,9 +222,9 @@ NAME                      READY   STATUS    RESTARTS   AGE
 prometheus-prometheus-0   3/3     Running   1          63m
 ```
 
-Prometheus server is running on port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
-Run following command on a separate terminal to forward 9090 port of `prometheus-prometheus-0` pod,
+Run following command on a separate terminal to forward the port 9090 of `prometheus-prometheus-0` pod,
 
 ```console
 $ kubectl port-forward -n monitoring prometheus-prometheus-0 9090

docs/guides/memcached/monitoring/using-builtin-prometheus.md

@@ -122,7 +122,7 @@ prometheus.io/port: 56790
 prometheus.io/scrape: true
 ```
 
-The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from exporter.
+The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from the exporter.
 
 ## Configure Prometheus Server
 
@@ -270,7 +270,7 @@ deployment.apps/prometheus created
 
 ### Verify Monitoring Metrics
 
-Prometheus server is running on port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
 At first, let's check if the Prometheus pod is in `Running` state.
 

docs/guides/memcached/monitoring/using-coreos-prometheus-operator.md

@@ -31,15 +31,15 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov
   namespace "demo" created
   ```
 
-- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you already don't have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
+- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you don't already have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
 
 - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server).
 
 > Note: YAML files used in this tutorial are stored in [docs/examples/memcached](https://github.com/kubedb/cli/tree/master/docs/examples/memcached) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli).
 
 ## Find out required labels for ServiceMonitor
 
-We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of Memcached crd so that KubeDB creates respective `ServiceMonitor` with these labels.
+We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of Memcached crd so that KubeDB creates `ServiceMonitor` object accordingly.
 
 At first, let's find out the available Prometheus server in our cluster.
 
@@ -224,9 +224,9 @@ NAME                      READY   STATUS    RESTARTS   AGE
 prometheus-prometheus-0   3/3     Running   1          63m
 ```
 
-Prometheus server is running on port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
-Run following command on a separate terminal to forward 9090 port of `prometheus-prometheus-0` pod,
+Run following command on a separate terminal to forward the port 9090 of `prometheus-prometheus-0` pod,
 
 ```console
 $ kubectl port-forward -n monitoring prometheus-prometheus-0 9090

docs/guides/mongodb/monitoring/using-builtin-prometheus.md

@@ -120,7 +120,7 @@ prometheus.io/port: 56790
 prometheus.io/scrape: true
 ```
 
-The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from exporter.
+The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from the exporter.
 
 ## Configure Prometheus Server
 
@@ -268,7 +268,7 @@ deployment.apps/prometheus created
 
 ### Verify Monitoring Metrics
 
-Prometheus server is running on port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
 At first, let's check if the Prometheus pod is in `Running` state.
 

docs/guides/mongodb/monitoring/using-coreos-prometheus-operator.md

@@ -32,15 +32,15 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov
   namespace "demo" created
   ```
 
-- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you already don't have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
+- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you don't already have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
 
 - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server).
 
 > Note: YAML files used in this tutorial are stored in [docs/examples/mongodb](https://github.com/kubedb/cli/tree/master/docs/examples/mongodb) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli).
 
 ## Find out required labels for ServiceMonitor
 
-We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of MongoDB crd so that KubeDB creates respective `ServiceMonitor` with these labels.
+We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of MongoDB crd so that KubeDB creates `ServiceMonitor` object accordingly.
 
 At first, let's find out the available Prometheus server in our cluster.
 
@@ -223,9 +223,9 @@ NAME                      READY   STATUS    RESTARTS   AGE
 prometheus-prometheus-0   3/3     Running   1          63m
 ```
 
-Prometheus server is running on port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
-Run following command on a separate terminal to forward 9090 port of `prometheus-prometheus-0` pod,
+Run following command on a separate terminal to forward the port 9090 of `prometheus-prometheus-0` pod,
 
 ```console
 $ kubectl port-forward -n monitoring prometheus-prometheus-0 9090

docs/guides/mysql/monitoring/using-builtin-prometheus.md

@@ -119,7 +119,7 @@ prometheus.io/port: 56790
 prometheus.io/scrape: true
 ```
 
-The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from exporter.
+The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from the exporter.
 
 ## Configure Prometheus Server
 
@@ -267,7 +267,7 @@ deployment.apps/prometheus created
 
 ### Verify Monitoring Metrics
 
-Prometheus server is running on port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
 At first, let's check if the Prometheus pod is in `Running` state.
 

docs/guides/mysql/monitoring/using-coreos-prometheus-operator.md

@@ -32,15 +32,15 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov
   namespace "demo" created
   ```
 
-- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you already don't have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
+- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you don't already have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
 
 - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server).
 
 > Note: YAML files used in this tutorial are stored in [docs/examples/mysql](https://github.com/kubedb/cli/tree/master/docs/examples/mysql) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli).
 
 ## Find out required labels for ServiceMonitor
 
-We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of MySQL crd so that KubeDB creates respective `ServiceMonitor` with these labels.
+We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of MySQL crd so that KubeDB creates `ServiceMonitor` object accordingly.
 
 At first, let's find out the available Prometheus server in our cluster.
 
@@ -222,9 +222,9 @@ NAME                      READY   STATUS    RESTARTS   AGE
 prometheus-prometheus-0   3/3     Running   1          63m
 ```
 
-Prometheus server is running on port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
-Run following command on a separate terminal to forward 9090 port of `prometheus-prometheus-0` pod,
+Run following command on a separate terminal to forward the port 9090 of `prometheus-prometheus-0` pod,
 
 ```console
 $ kubectl port-forward -n monitoring prometheus-prometheus-0 9090

docs/guides/postgres/monitoring/using-builtin-prometheus.md

@@ -120,7 +120,7 @@ prometheus.io/port: 56790
 prometheus.io/scrape: true
 ```
 
-The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from exporter.
+The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from the exporter.
 
 ## Configure Prometheus Server
 
@@ -268,7 +268,7 @@ deployment.apps/prometheus created
 
 ### Verify Monitoring Metrics
 
-Prometheus server is running on port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
 At first, let's check if the Prometheus pod is in `Running` state.
 

docs/guides/postgres/monitoring/using-coreos-prometheus-operator.md

@@ -31,15 +31,15 @@ CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) prov
   namespace "demo" created
   ```
 
-- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you already don't have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
+- We need a CoreOS [prometheus-operator](https://github.com/coreos/prometheus-operator) instance running. If you don't already have a running instance, deploy one following the docs from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md).
 
 - If you already don't have a Prometheus server running, deploy one following tutorial from [here](https://github.com/appscode/third-party-tools/blob/master/monitoring/prometheus/coreos-operator/README.md#deploy-prometheus-server).
 
 > Note: YAML files used in this tutorial are stored in [docs/examples/postgres](https://github.com/kubedb/cli/tree/master/docs/examples/postgres) folder in GitHub repository [kubedb/cli](https://github.com/kubedb/cli).
 
 ## Find out required labels for ServiceMonitor
 
-We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of PostgreSQL crd so that KubeDB creates respective `ServiceMonitor` with these labels.
+We need to know the labels used to select `ServiceMonitor` by a `Prometheus` crd. We are going to provide these labels in `spec.monitor.prometheus.labels` field of PostgreSQL crd so that KubeDB creates `ServiceMonitor` object accordingly.
 
 At first, let's find out the available Prometheus server in our cluster.
 
@@ -222,9 +222,9 @@ NAME                      READY   STATUS    RESTARTS   AGE
 prometheus-prometheus-0   3/3     Running   1          63m
 ```
 
-Prometheus server is running on port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090` of `prometheus-prometheus-0` pod. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
-Run following command on a separate terminal to forward 9090 port of `prometheus-prometheus-0` pod,
+Run following command on a separate terminal to forward the port 9090 of `prometheus-prometheus-0` pod,
 
 ```console
 $ kubectl port-forward -n monitoring prometheus-prometheus-0 9090

docs/guides/redis/monitoring/using-builtin-prometheus.md

@@ -119,7 +119,7 @@ prometheus.io/port: 56790
 prometheus.io/scrape: true
 ```
 
-The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from exporter.
+The Prometheus server will discover the service endpoint using these specifications and will scrape metrics from the exporter.
 
 ## Configure Prometheus Server
 
@@ -267,7 +267,7 @@ deployment.apps/prometheus created
 
 ### Verify Monitoring Metrics
 
-Prometheus server is running on port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
+Prometheus server is listening to port `9090`. We are going to use [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) to access Prometheus dashboard.
 
 At first, let's check if the Prometheus pod is in `Running` state.