Minor wording changes to MarkDown documents

Signed-off-by: Anthony D'Atri <anthonyeleven@users.noreply.github.com>

INSTALL.md

@@ -1,9 +1,9 @@
 Installation Instructions for procps
 ====================================
-Depending on what format you are using to get these files, you
-might need to run the `autogen.sh` program to create the
+Depending on how you retrieve this code you
+may need to run the `autogen.sh` program to create the
 configure script. If you have a configure script already then
-you might not need it.
+you may not need to do this.
 
 A typical installation would go something like
 

README.md

@@ -4,23 +4,23 @@ procps
 
 procps is a set of command line and full-screen utilities that provide
 information out of the pseudo-filesystem most commonly located at /proc.
-This filesystem provides a simple interface to the kernel data structures.
-The programs of procps generally concentrate on the structures that describe
-the processess running on the system.
+This filesystem provides a simple interface to kernel data structures.
+The utilities provided by procps focus on the structures that describe
+processess running on the system.
 
-The following programs are found in procps:
-* *free* - Report the amount of free and used memory in the system
-* *hugetop* - Report the huge page information of system and processes
+The following utilities are provided by procps:
+* *free* - Report the amounts of free and used memory in the system
+* *hugetop* - Report hugepage usage of processes and the system as a whole
 * *kill* - Send a signal to a process based on PID
 * *pgrep* - List processes based on name or other attributes
 * *pkill* - Send a signal to a process based on name or other attributes
-* *pmap* - Report memory map of a process
-* *ps* - Report information of processes
-* *pwdx* - Report current directory of a process
+* *pmap* - Report the memory map of a process
+* *ps* - Report process information including PID and resource usage
+* *pwdx* - Report the current working directory of a process
 * *skill* - Obsolete version of pgrep/pkill
 * *slabtop* - Display kernel slab cache information in real time
 * *snice* - Renice a process
-* *sysctl* - Read or Write kernel parameters at run-time
+* *sysctl* - Read or write kernel parameters at run-time
 * *tload* - Graphical representation of system load average
 * *top* - Dynamic real-time view of running processes
 * *uptime* - Display how long the system has been running
@@ -29,18 +29,18 @@ The following programs are found in procps:
 * *watch* - Execute a program periodically, showing output fullscreen
 
 ## Reporting Bugs
-There are a few ways of reporting bugs or feature requests:
+There are three ways to submit bugs or feature requests:
 
-1. Your distribution's bug reporter. If you are using a distribution your first
-port of call is their bug tracker. This is because each distribution has their
-own patches and way of dealing with bugs. Also bug reporting often does not need
-any subscription to websites.
+1. Your Linux distribution's bug reporter. If you are using Linux distribution
+packages your first port of call is their bug tracker. This is because each
+distribution has their own patches and way of dealing with bugs. Also bug
+reporting often does not need any subscription to websites.
 2. GitLab Issues - To the left of this page is the issue tracker. You can report
 bugs here.
 3. Email list - We have an email list (see below) where you can report bugs.
-The problem with this method is bug reports often get lost and cannot be
-tracked. This is especially a big problem when its something that will take
-time to resolve.
+A shortcoming of this method is that such bug reports often get lost and cannot
+be tracked. This is especially problematic when the report conerns something
+that will take time to resolve.
 
 If you need to report bugs, there is more details on the
 [Bug Reporting](https://gitlab.com/procps-ng/procps/blob/master/Documentation/bugs.md)