Updated language use in test-suite.md

Author: Ed Stenson

doc/cprover-manual/test-suite.md

@@ -24,7 +24,7 @@ suite generation functionality in CBMC, by means of a case study. The
 following program is an excerpt from a real-time embedded benchmark
 [PapaBench](https://www.irit.fr/recherches/ARCHI/MARCH/rubrique.php3?id_rubrique=97),
 and implements part of a fly-by-wire autopilot for an Unmanned Aerial
-Vehicle (UAV). We have adjusted slightly for our purposes.
+Vehicle (UAV). We have adjusted it slightly for our purposes.
 
 The aim of function `climb_pid_run` is to control the vertical climb of
 the UAV. Details on the theory behind this operation are documented in
@@ -133,7 +133,7 @@ following command:
 We'll describe those command line options one by one. The option `--cover mcdc`
 specifies the code coverage criterion. There
 are four conditional statements in the PID function: in lines 41,
-44, 48 and 49. To satisfy MC/DC, the test suite has to meet
+44, 48, and 49. To satisfy MC/DC, the test suite has to meet
 multiple requirements. For instance, each conditional statement needs to
 evaluate to *true* and *false*. Consider the condition
 `"pprz>=0 && pprz<=MAX_PPRZ"` in line 41. CBMC instruments three