diff options
| -rw-r--r-- | www/hall-of-shame.html | 2 | ||||
| -rw-r--r-- | www/reliability.html | 4 |
2 files changed, 3 insertions, 3 deletions
diff --git a/www/hall-of-shame.html b/www/hall-of-shame.html index ad06e424..15cd0891 100644 --- a/www/hall-of-shame.html +++ b/www/hall-of-shame.html @@ -114,7 +114,7 @@ quality (or, rather, utter <em>lack</em> of quality) of their chipset documentation. You would think they'd have figured out by now that good and readily available documentation, making it easy for others to interface to their hardware, will sell more hardware. But no; most -vendors make documentation difficult to get, and it rends to be both +vendors make documentation difficult to get, and it tends to be both incomplete and vague when you get it. A few vendors go above and beyond the normal stupidity...</p> diff --git a/www/reliability.html b/www/reliability.html index 27b72916..70dc2916 100644 --- a/www/reliability.html +++ b/www/reliability.html @@ -81,7 +81,7 @@ for months between new tracker bugs.</p> <h2>We have an extensive suite of unit tests and regression tests</h2> -<p>GPSD has around 90 unit tests and regression tests, including sample +<p>GPSD has around 100 unit tests and regression tests, including sample device output for almost every sensor type we support. We've put a lot of effort into making the tests easy and fast to run so they can be run often. This makes it actively difficult for random code changes to @@ -132,7 +132,7 @@ small a fraction of the state space as we can.</p> <p>We also use <a href='http://valgrind.org/'>valgrind</a> to check for memory leaks, though this is not expected to turn up bugs (and -doesn't) due to our no-dynamic-allocation <a href="hacking#malloc">house +doesn't) due to our no-dynamic-allocation <a href="hacking#malloc.html">house rule</a>.</p> <h2>We are methodical and merciless</h2> |