Fix typos, grammar in *.md files

Clean up some incorrect statements as well, mostly
by deleting them.

Author: ndokos

README.md

@@ -67,7 +67,7 @@ https://github.com/distributed-system-analysis/pbench/milestones).
 
 Below are some simple steps for setting up a development environment for
 working with the Pbench code base.  For more detailed instructions on the
-workflow and process of contributing code to Pbench, refere to the [Guidelines
+workflow and process of contributing code to Pbench, refer to the [Guidelines
 for Contributing](doc/CONTRIBUTING.md).
 
 ### Getting the Code
@@ -85,17 +85,17 @@ execute:
  * `jenkins/run jenkins/tox -r --current-env -e jenkins-pytests`
  * `jenkins/run jenkins/tox -r --current-env -e jenkins-unittests`
 
-The above commands runs the tests in a Fedora-base container with all the
+The above commands run the tests in a Fedora-base container with all the
 proper packages installed.
 
-If you want to run the Unit Tests outside of that environment, you need to
+If you want to run the unit tests outside of that environment, you need to
 install `tox` properly in your environment (Fedora/CentOS/RHEL):
 
 ```
 $ sudo dnf install -y perl-JSON python3-pip python3-tox
 ```
 
-Once tox is installed you can run the unittests (use `tox --listenvs` to see
+Once tox is installed you can run the unit tests (use `tox --listenvs` to see
 the full list); e.g.:
 
   * `tox -e util-scripts`  -- for agent/util-scripts tests

agent/tool-scripts/README.md

@@ -32,7 +32,7 @@ for executing all the "persistent" tools.  Once the Tool Meister sub-system is
 up and running, this phase is started first (required), and is ended before
 the Tool Meister sub-system is shut down (required).  The `pbench-init-tools`
 CLI interface begins the "persistent" tools phase, and the `pbench-end-tools`
-closes out the phase.  More about "persistent" tools below.
+CLI interface closes out the phase.  More about "persistent" tools below.
 
 The second phase is for executing all the "transient" tools (described below).
 This phase must be started after the "persistent" tools phase begins, and must
@@ -109,7 +109,7 @@ post-processing at a later time:
   $
   $ pbench-end-tools
   $
-  $ # All data has been collected, run the all the post-processing locally.
+  $ # All data has been collected, run all the post-processing locally.
   $
   $ pbench-postprocess-tools
   $ pbench-postprocess-tools
@@ -132,15 +132,15 @@ those tools registered.
 ### The `node-exporter` and `dcgm` Tools
 
 The `node-exporter` and `dcgm` tool scripts provided in this directory are
-placeholders only in order for users to see them along side the other tools.
+placeholders only in order for users to see them alongside the other tools.
 The actual implementation of these tools is handled by the Tool Meister code
 directly.
 
 ## Transient Tools
 
 A "transient" tool is one where the tool data capture happens on the host
 local to where the tool is running.  All transient tools store their data
-locally as directed by its invoking Tool Meister.  For Tool Meisters running
+locally as directed by their invoking Tool Meister.  For Tool Meisters running
 on the same host where the caller is driving the benchmark (where
 `pbench-tool-meister-start` was invoked), the captured data is stored directly
 into the local `${benchmark_result_dir}` directory.  Tool Meisters running on
@@ -177,7 +177,7 @@ handles the required steps for properly capturing all of the relevant data and
 meta-data for that tool.  These scripts are stored in the "postprocess"
 sub-directory named `<tool>-stop-postprocess`.  The `stop-postprocess` script
 is executed on the host running the tool, after that tool is stopped
-successfully, but before reporting back to the caller the tool has stopped.
+successfully, but before reporting back to the caller that the tool has stopped.
 
 Similarly, each transient tool can also optionally provide a "postprocess"
 script which handles post-processing steps for the captured data to apply any
@@ -189,7 +189,7 @@ when the `pbench-postprocess-tools` script is invoked.
 In cases where your operating system distribution does not provide a package
 for installing the Prometheus `node_exporter` command, consider following the
 steps below on the hosts from which you want to collect Prometheus
-`node_exporter`, and/or refer to the `node_exporter` [GitHub source
+`node_exporter` data, and/or refer to the `node_exporter` [GitHub source
 repository](https://github.com/prometheus/node_exporter).
 
  1. `wget https://github.com/prometheus/node_exporter/releases/download/v1.0.1/node_exporter-1.0.1.linux-amd64.tar.gz`  (latest version, change version number as desired)

doc/CONTRIBUTING.md

@@ -67,12 +67,12 @@ the report as well, and they have been updated accordingly.
 1. Write appropriate Pull Request Title stating the fix
   1. Use present tense (ex. Fixes, Changes, Fixing, Changing..)
 1. Reference the issue that the PR is fixing with **“Fixes #issue_number”** in the description
-1. Provide a detailed description (at least 50 - 70 characters) of the changes; if UI related, add screenshots or gif
+1. Provide a detailed description of the changes; if UI related, add screenshots
 1. Make sure that the branches can be automatically merged (otherwise rebase the PR with `master`) and then click the drop down next to, `Create pull request`, and select `Create draft pull request`
 ![Image](https://lh5.googleusercontent.com/V14SjFhimKYF1fH6TXMfaoZtDCj2ZH0d9USqe8YHyn0xOOVYekiXtx2CwdOQbSvxWPB6JVEfi4jSM_mjkSMaaI7voQNYQ8gDWntMhzCMbj3wrK3H4eCSEsdVq_XP_aZMdb5h9xU4)
 
 1. Assign the PR to yourself and add appropriate labels
-1. Add "**DO NOT MERGE**" label if the work is not needed to be merged or there is no agreement on the work yet
+1. Add "**DO NOT MERGE**" label if the work does not need to be merged or there is no agreement on the work yet
 1. Make sure to add Milestone to the PR to mention specific release
 1. Request for review once the work is ready for getting reviewed
 ![Image](https://lh6.googleusercontent.com/iM-vaIsFQ8ew7vpNDUvmSY9MVjyTadTZkngdlQfo7qYe_QQuFSA8yZ_3P40fBdeNw6Q-lSJwDD59jfBoQgdNP3mGHPgrjVicsyGt8QkMMAaDYowHsIyAnukXsEiFPSOnYnrZyze3)
@@ -82,7 +82,6 @@ the report as well, and they have been updated accordingly.
 1. Make sure to add proper details to the Issue raised
 1. Upload screenshot(if possible) in dashboard issues
 1. Apply proper labels to the Issue
-1. Make sure to add Milestone and Project to the issue to mention specific release.
 1. Try to actively respond to the communication in case of comments in the same issue.
 
 ## Reviewing a pull request