Add two more regression tests. Pre-release doc cleanup.

1 files changed, 4 insertions, 4 deletions

diff --git a/www/excellence.html b/www/excellence.html
index f1bcfb9b..550c326d 100644
--- a/www/excellence.html
+++ b/www/excellence.html
@@ -138,8 +138,8 @@ practice that extends all the way up from our development habits to
 the zero-configuration design of the gpsd daemon.</p>
 
 <p>The most important thing we do to ensure code quality is maintain a
-rigorous test suite.  Our "make testregress" runs about fifty-five
-regression and unit tests.  Forty-four of those exercise the daemon's
+rigorous test suite.  Our "make testregress" runs just shy of sixty
+regression and unit tests.  Forty-six of those exercise the daemon's
 logic for recognizing and processing device reports; the remaining ten
 to a dozen exercise the rest of the code, all the way out to the
 application service libraries.</p>
@@ -228,8 +228,8 @@ effects of autoconfiguration ripple through dozens of
 application-development groups and all the way up the software stack
 to the end-user.</p>
 
-<p>Finally, the RFP for these essays asked software authors to explain
-what they'd do with a $500 prize.  That's easy; we'd use it to <a
+<p>The RFP for these essays asked software authors to explain what
+they'd do with a $500 prize.  That's easy; we'd use it to <a
 href="wishlist.html">buy test hardware</a>. Because GPSes are wacky,
 idiosyncratic devices with poorly documented interfaces, testing on
 real hardware is vital to fully learn their quirks.</p>