Review the documentation for Prometheus Input Package (#14668)

* Review the readme

* Update changelog and manifest

* Integrate reviewer's comments

Author: alaudazzi

packages/prometheus_input/changelog.yml

@@ -1,4 +1,9 @@
 # newer versions go on top
+- version: "0.9.1"
+  changes:
+    - description: Review the documentation for Prometheus Input Package.
+      type: enhancement
+      link: https://github.com/elastic/integrations/pull/14668
 - version: "0.9.0"
   changes:
     - description: Add SSL configuration options.

packages/prometheus_input/docs/README.md

@@ -1,27 +1,23 @@
 # Prometheus Input Package
 
-This input package can collect metrics from [Prometheus Exporters (Collectors)](https://prometheus.io/docs/instrumenting/exporters/). It gives users the flexibility to add custom mappings and ingest pipelines.
+The Prometheus Input package allows you to collect metrics from [Prometheus Exporters (Collectors)](https://prometheus.io/docs/instrumenting/exporters/) and gives you the flexibility to add custom mappings and ingest pipelines.
 
 ## Metrics
 
-#### Scraping from a Prometheus exporter
+#### Collect metrics from a Prometheus exporter
 
-To scrape metrics from a Prometheus exporter, configure the `hosts` setting to it. The path
-to retrieve the metrics from (`/metrics` by default) is appended to the hostname as below:
+To collect metrics from a Prometheus exporter, configure the `hosts` setting to it and append the <metrics_path> from which you are collecting your metrics (`/metrics` by default), by using the following format: 
+- `http[s]://<hostname>:<port>/<metrics_path>`
 
-Host Configuration Format: `http[s]://<hostname>:<port>/<metrics_path>`
-Example Host Configuration: `http://localhost:9090/metrics`
+This is an example of host configuration: `http://localhost:9090/metrics`
 
 #### Histograms and types
 
-`Use Types` parameter (default: `true`) enables a different layout for metrics storage, leveraging Elasticsearch
-types, including [histograms](https://www.elastic.co/guide/en/elasticsearch/reference/current/histogram.html)
+The parameter `Use Types` (default: `true`) enables a different layout for metrics storage, leveraging Elasticsearch types, including [histograms](https://www.elastic.co/guide/en/elasticsearch/reference/current/histogram.html).
 
-`Rate Counters` parameter (default: `true`) enables calculating a rate out of Prometheus counters. When enabled, integration stores
-the counter increment since the last collection. This metric provides better aggregation. 
-This parameter can only be enabled in combination with `Use Types`.
+The parameter `Rate Counters` (default: `true`) allows you to calculate a rate out of Prometheus counters. When enabled, integration stores the counter increment since the last collection. This metric provides better aggregation. This parameter can only be enabled in combination with the parameter `Use Types`.
 
-When `Use Types` and `Rate Counters` are enabled, metrics are stored like this:
+When `Use Types` and `Rate Counters` are enabled, metrics are stored as follows:
 
 ```json
 {
@@ -51,7 +47,7 @@ When `Use Types` and `Rate Counters` are enabled, metrics are stored like this:
 
 #### Filtering metrics
 
-In order to filter out/in metrics one can make use of `Metrics Filters Include`, `Metrics Filters Exclude` settings:
+To filter out/in metrics, you can use the following settings:
 
 ```yml
 Metrics Filters Include: ["node_filesystem_*"]
@@ -60,15 +56,15 @@ Metrics Filters Exclude: ["node_filesystem_device_*"]
 
 The configuration above will include only metrics that match `node_filesystem_*` pattern and do not match `node_filesystem_device_*`.
 
-
 To keep only specific metrics, anchor the start and the end of the regexp of each metric:
 
-- the caret ^ matches the beginning of a text
-- the dollar $ matches the end of a text
+- the caret sign `^` matches the beginning of a text
+- the dollar sign `$` matches the end of a text
 
 ```yml
 Metrics Filters Include: ["^node_network_net_dev_group$", "^node_network_up$"]
 ```
 
-### Datastream Dataset Name
-The users of the Prometheus Input Package have the option of adding their own dataset name, to which the events get added. Prometheus Metrics from different services can be collected by adding multiple instances of Input package. The metrics can be filtered on the basis of dataset name.
+### Datastream dataset name
+
+By using the Prometheus Input Package, you can add your own dataset name, to which the events get added. You can collect Prometheus metrics from different services by adding multiple instances of the Input package. Metrics can be filtered based on the dataset name.

packages/prometheus_input/manifest.yml

@@ -1,7 +1,7 @@
 format_version: "3.0.2"
 name: prometheus_input
 title: "Prometheus Input"
-version: "0.9.0"
+version: "0.9.1"
 description: "Collects metrics from Prometheus exporter."
 type: input
 categories: