summaryrefslogtreecommitdiff
path: root/gps.xml
diff options
context:
space:
mode:
authorJon Schlueter <jon.schlueter@gmail.com>2011-03-05 05:10:52 -0500
committerJon Schlueter <jon.schlueter@gmail.com>2011-03-05 05:10:52 -0500
commitd84fbd511ed2d0e78437249fb561ce9bd91e4077 (patch)
tree5055362610294ed7ca49e51fcbf79ad46512f0db /gps.xml
parent535a32e6a6b4150abdc0307ffb9947425927dc55 (diff)
downloadgpsd-d84fbd511ed2d0e78437249fb561ce9bd91e4077.tar.gz
spellchecking in gps.xml
Diffstat (limited to 'gps.xml')
-rw-r--r--gps.xml10
1 files changed, 5 insertions, 5 deletions
diff --git a/gps.xml b/gps.xml
index efb9715a..0ba93d12 100644
--- a/gps.xml
+++ b/gps.xml
@@ -128,7 +128,7 @@ decimal minutes. The value 's' produces degrees, minutes, and decimal
seconds.</para>
<para><application>xgps</application>,
-<application>cgps</application>, and <application>ldcgps</application>
+<application>cgps</application>, and <application>lcdgps</application>
look at variables in the environment to figure out what units they
should default to using for display &mdash; imperial, nautical, or
metric. Here are the variables and values they check:</para>
@@ -157,27 +157,27 @@ the system units for display; follow the keyword with 'i' for
'imperial' for American units (feet in altitude and error estimates,
miles per hour in speeds), 'n' for 'nautical' (feet in altitude and
error estimates, knots in speed) or 'm' for 'metric' (meters in
-altitude and error estimates, kiliometers per hour in speeds). </para>
+altitude and error estimates, kilometers per hour in speeds). </para>
<para> The <option>-D</option> option, when present, sets a debug
level; it is primarily for use by GPSD developers. It enables
various progress messages to standard error.</para>
<para>By default, clients collect data from all compatible devices on
-localhost, using the defalt GPSD port 2947. An optional argument to any
+localhost, using the default GPSD port 2947. An optional argument to any
client may specify a server to get data from. A colon-separated suffix
is taken as a port number. If there is a second colon-separated
suffix, that is taken as a specific device name to be
watched. However, if the server specification contains square
brackets, the part inside them is taken as an IPv6 address and
-port/device suffixes are obnly parsed after the trailing bracket.
+port/device suffixes are only parsed after the trailing bracket.
Possible cases look like this:</para>
<variablelist>
<varlistentry>
<term>localhost:/dev/ttyS1</term>
<listitem><para>Look at the default port of localhost, trying both
-IPv4 and IPv6 and watching ouput from serial device 1.</para></listitem>
+IPv4 and IPv6 and watching output from serial device 1.</para></listitem>
</varlistentry>
<varlistentry>
<term>example.com:2317</term>