summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJon Schlueter <jon.schlueter@gmail.com>2011-03-05 15:09:49 -0500
committerJon Schlueter <jon.schlueter@gmail.com>2011-03-05 15:09:49 -0500
commit1d6576a2809e0e8c7e593a58e6ef38c3ff347b23 (patch)
treeb7e0882bef9f714dbeab7c8988e8c9e9d4741803
parent3f56ad9c644c0a5f26aa3ef11a1df9dd1a26abe3 (diff)
downloadgpsd-1d6576a2809e0e8c7e593a58e6ef38c3ff347b23.tar.gz
spellchecking of gypsy.html
-rw-r--r--www/gypsy.html4
1 files changed, 2 insertions, 2 deletions
diff --git a/www/gypsy.html b/www/gypsy.html
index 5c424f7c..0f6ca992 100644
--- a/www/gypsy.html
+++ b/www/gypsy.html
@@ -67,7 +67,7 @@ href="http://gypsy.freedesktop.org/why-not-gpsd.html">Why Should You
Use Gypsy over GPSD</a>, to which this note is intended as a
reply.</p>
-<p>We'll start off by acknowldeging that Holmes's critique raises one
+<p>We'll start off by acknowledging that Holmes's critique raises one
or two valid points. For the specific cases of interactive
applications running on a Linux system, communicating via D-Bus
signals makes sense. Holmes somehow misses the fact that GPSD has
@@ -102,7 +102,7 @@ vendor GPS protocols (and autoconfiguring the service layer to do it)
is a difficult job that took us years to get good at.
<p>The odds that Holmes or anyone else could get ahead of GPSD on this
-learning curve are, frankly, miniscule. And the odds of anyone
+learning curve are, frankly, minuscule. And the odds of anyone
duplicating the infrastructure of regression tests, simulators, and
other tools that we use to verify GPSD's behavior against that
large range of devices and protocol types are even lower.</p>