Minor updates to the README

Signed-off-by: Matt Cantu Snell <msnell@unomaha.edu>

README.md

@@ -4,7 +4,7 @@
 
 GrimoireLab is a [CHAOSS](https://chaoss.community) toolset for software development analytics. It includes a coordinated set of tools
 to retrieve data from systems used to support software development (repositories), store it in databases,
-enrich it by computing relevant metrics and making it easy to run analytics and visualizations on it.
+enrich it by computing relevant metrics, and make it easy to run analytics and visualizations on it.
 
 You can learn more about GrimoireLab in the [GrimoireLab tutorial](https://chaoss.github.io/grimoirelab-tutorial/),
 or visit the [GrimoireLab website](https://chaoss.github.io/grimoirelab).
@@ -13,8 +13,8 @@ Metrics available in GrimoireLab are, in part, developed in the CHAOSS project.
 
 # Getting started
 
-GrimoireLab is a set of tools, and to ease starting playing we are providing a [default setup](default-grimoirelab-settings)
-to analyze git activity for this repository. Given such set up, there are several options to run GrimoireLab:
+To ease the newcomer experience we are providing a [default setup](default-grimoirelab-settings)
+to analyze git activity for this repository. For this set up, there are several options to run GrimoireLab:
 
 ## Using `docker-compose`
 
@@ -28,7 +28,7 @@ Docker version 19.03.1, build 74b1e89
 root@test-68b8628f:~# docker-compose --version
 docker-compose version 1.22.0, build f46880fe
 ```
-* **Hardware**: 2 CPUs, 8GB memory RAM and [enough virtual memory for Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html) 
+* **Hardware**: 2 CPU cores, 8GB memory RAM and [enough virtual memory for Elasticsearch](https://www.elastic.co/guide/en/elasticsearch/reference/current/vm-max-map-count.html) 
 
 Steps:
 1. Clone this project:
@@ -55,7 +55,7 @@ git version 2.17.1
 root@test-68b8628f:~# docker --version
 Docker version 19.03.1, build 74b1e89
 ```
-* **Hardware**: 2 CPUs, 8GB memory RAM and set
+* **Hardware**: 2 CPU cores, 8GB memory RAM and set
 
 Steps:
 1. Clone this project:
@@ -109,11 +109,11 @@ which can be useful for you. Other related repositories are:
 
 ## Contents of this repository
 
-This repository is for stuff relevant to GrimoireLab as a whole. For example:
+This repository is for content relevant to GrimoireLab as a whole. For example:
 
-* Issues for new features or bug reports that affect more than one GrimoireLab module. In this case, let's open an issue here, and when implementing the fix or the feature, let´s comment about the specific tickets in the specific modules that are used. For example, when supporting a new datasource, we will need patches (at least) in `Perceval`, `GrimoireELK` and panels. We would open here the feature request (or the user story) for the whole case, an issue (and later a pull request) in `Perceval` for the data retriever, same for `GrimoireELK` for the enriching code, and same for `panels` for the Kibiter panels.
+* Issues for new features or bug reports that affect more than one GrimoireLab module. In this case, let's open an issue here, and when implementing the fix or the feature, let´s comment about the specific tickets in the specific modules that are used. For example, when supporting a new datasource, we will need patches (at least) in `Perceval`, `GrimoireELK` and panels. In this case, we would open a feature request (or the user story) for the whole case, an issue (and later a pull request) in `Perceval` for the data retriever, same for `GrimoireELK` for the enriching code, and same for `panels` for the Kibiter panels.
 
-* Information about "coordinated releases" for most of GrimoireLab components
+* Information about "coordinated releases" for most GrimoireLab components
 (directory [releases](releases)).
 Coordinated releases are snapshots (specific commits)
 of most of the GrimoireLab components that are expected to work together.