summaryrefslogtreecommitdiff
path: root/www/writing-a-driver.xml
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2006-11-11 22:04:15 +0000
committerEric S. Raymond <esr@thyrsus.com>2006-11-11 22:04:15 +0000
commit2f17f3fd23a85b6954c0530c568e63c332b7f6f7 (patch)
tree458576a92692b3157a070f1878bd6211282094ab /www/writing-a-driver.xml
parent64bdd0b91f4450a516f18c1244ea1e863b85b9aa (diff)
downloadgpsd-2f17f3fd23a85b6954c0530c568e63c332b7f6f7.tar.gz
Typo fix pointed out by Bill Marr.
Diffstat (limited to 'www/writing-a-driver.xml')
-rw-r--r--www/writing-a-driver.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/www/writing-a-driver.xml b/www/writing-a-driver.xml
index 90edd036..51133357 100644
--- a/www/writing-a-driver.xml
+++ b/www/writing-a-driver.xml
@@ -55,7 +55,7 @@ lot of work and research on your own.</para>
<para>I found that the device I wanted to use (a Navman Jupiter-T) was
not supported in its default operation mode. The device actually
provides two other supported modes, NMEA (exceptional support) and
-Rockwell/Conextant/Navman binary (supported by the Earthmate driver
+Rockwell/Conexant/Navman binary (supported by the Earthmate driver
<filename>zodiac.c</filename>), I could have possibly avoided
writing a driver by switching to one of these modes, but there was an
overwhelming reason to use the unsupported default mode.</para>
@@ -111,7 +111,7 @@ external computing device and provide raw navigation and time data,
but the interfaces and control language were superbly specified in a
well written technical document of about 200 pages. In actual fact the
document I used most was the Motorola documentation for the default
-Oncore mode, but the NMEA and Rockwell/Conextant/Navman modes were
+Oncore mode, but the NMEA and Rockwell/Conexant/Navman modes were
equally well documented in the Navman manuals.</para>
<para>You will also need to set aside some time