Documentation updates

Author: akoutmos

README.md

@@ -64,7 +64,7 @@ Documentation can be found at [https://hexdocs.pm/prom_ex](https://hexdocs.pm/pr
 
 ## Supporting PromEx
 
-PromEx has an ambition goal: To provide Prometheus metrics and Grafana dashboards for as many of the libraries in the Elixir ecosystem as possible as well as a framework so that you can manage the lifecycle of your own metrics and dashboards.
+PromEx has an ambitious goal: To provide Prometheus metrics and Grafana dashboards for as many of the libraries in the Elixir ecosystem as possible as well as a framework so that you can manage the lifecycle of your own metrics and dashboards.
 
 If you rely on PromEx to monitor your production applications, it would much appreciated if you can give back to the
 project in order to help ensure its continued development.
@@ -89,7 +89,7 @@ project in order to help ensure its continued development.
 
 ## Setting Up PromEx
 
-The goal of PromEx is to have metrics set up be as simple and streamlined as possible. In that spirit, all
+The goal of PromEx is to make the process of setting up metrics as easy as possible. In that spirit, all
 that you need to do to start leveraging PromEx along with the built-in plugins is to run the following mix
 task (the `YOUR_PROMETHEUS_DATASOURCE_ID` value should align with what is configured in Grafana as the name of the
 Prometheus data source):

guides/howtos/Writing PromEx Plugins.md

@@ -22,7 +22,7 @@ provided to the struct `build` function.
 
 To have your custom plugin expose event based metrics, implement a `event_metrics/1` function and build out a collection
 of `Telemetry.Metrics` structs (`distribution`, `counter`, `last_value`, and `sum`). Be sure to look at plugins like
-`PromEx.Plugins.Phoenix` for more in depth examples.
+`PromEx.Plugins.Phoenix` for more in-depth examples.
 
 ```elixir
 defmodule MyApp.PromEx.Plugins.MyPhoenix do
@@ -61,7 +61,7 @@ end
 ## Adding Polling Metrics
 
 Polling metrics are similar to event metrics in that they require similar fields (`group_name` and `metrics` to be
-specific). In addition, the `PromEx.MetricTypes.Polling.build/4` function requires an `measurements_mfa` argument which
+specific). In addition, the `PromEx.MetricTypes.Polling.build/4` function requires a `measurements_mfa` argument which
 specifies what function will be executed on the polling interval. This function should run `:telemetry.execute/3`
 somewhere in its function body. Once that event is executed, the corresponding event in the struct will be triggered and
 you will capture the desired data point. The following example from `PromEx.Plugins.Beam` should highlight this concept: