summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorPierre Grandin <grandinp@gmail.com>2019-06-05 12:11:15 -0600
committerPierre Grandin <grandinp@gmail.com>2019-06-05 12:11:15 -0600
commit43159bb248893ad02fe3a18de4df9c22212d2118 (patch)
treef0f7a223933e211a0bb6c4e6146381df9a8a30d0
parentbc1574c48ab8ba11bbdd47ad7cd539d3f9dc7f07 (diff)
downloadnavit-43159bb248893ad02fe3a18de4df9c22212d2118.tar.gz
Fixed some typos
-rw-r--r--docs/configuration/layout.rst2
-rw-r--r--docs/configuration/vehicle.rst8
2 files changed, 5 insertions, 5 deletions
diff --git a/docs/configuration/layout.rst b/docs/configuration/layout.rst
index b99dfafca..32e18f31d 100644
--- a/docs/configuration/layout.rst
+++ b/docs/configuration/layout.rst
@@ -30,7 +30,7 @@ For infos about map icons, see [[Icons]]
===Overriding default (shipped) layouts===
When the XML config file is parsed, layouts are taken in the order they come, and a layout with an already existing name overrides a previous definition.
-The default (shipped) navit.xml includes first system-wide navit_layout_*.xml files then the user-specific navit_layout_*.xml files, so the system-wide navit_layout_*.xml files can be overriden by adding a user-specific navit-layout_*.xml containing the same **name** attribute.
+The default (shipped) navit.xml includes first system-wide navit_layout_*.xml files then the user-specific navit_layout_*.xml files, so the system-wide navit_layout_*.xml files can be overiden by adding a user-specific navit-layout_*.xml containing the same **name** attribute.
Copying the default **navit.xml** file to the user-specific location will still use the default shipped layout files, but copying one or several layout files as well to the user-specific location (and modifying them) allow to override these specific layouts.
diff --git a/docs/configuration/vehicle.rst b/docs/configuration/vehicle.rst
index f8374f9ee..c4fbabc3f 100644
--- a/docs/configuration/vehicle.rst
+++ b/docs/configuration/vehicle.rst
@@ -23,7 +23,7 @@ Obsolete options:
-->
===GPS===
-Most esential detail is the gps source, that need to be adapted to your local setup.
+Most essential detail is the gps source, that need to be adapted to your local setup.
**Local:**
@@ -33,7 +33,7 @@ Windows:
** For Locosys GT31 (or BGT31 plugged by USB), settings are: source="serial:COM3 baud=38400 parity=N data=8 stop=1" where COM3 should be replaced by the correct COM over USB number.
Windows Mobile:
-* source="wince:GPD1:" - using the internal GPS driver, configured from Windows Remote GPS Settings.
+* source="wince:GPD1:" - using the internal GPS driver, configured from Windows Remote GPS Settings.
** To use a BT GPS it must be configured as outgoing com port and paired, then selected as hardware port in GPS Settings.
** To start bluetooth on navit startup add bluetooth="yes". When exiting navit, the previous bluetooth state is recovered.
* source="wince:COM1:" baudrate="57600"
@@ -43,7 +43,7 @@ There is useful [http://w5.nuinternet.com/s660100031/SirfTech.htm. SirfTech util
Linux:
* source="file:/dev/rfcomm0" - BlueTooth GPS
* source="file:/dev/ttyS0" - serial GPS connected to the first serial port (you may need to add the correct baudrate eg.: freerunner source="file:/dev/ttySAC1" baudrate="9600")
-* source="gpsd_dbus:" - via dbus, postion reported by gpsd
+* source="gpsd_dbus:" - via dbus, position reported by gpsd
**Network based:**<br>
If you want to connect multiple tools to your GPS, you need an multiplexer tool, as gpsd or gypsy.
@@ -59,7 +59,7 @@ If you want to connect multiple tools to your GPS, you need an multiplexer tool,
* source="demo://" : to use the demo vehicle. Set your Position and Destination, and vehicle will follow the calculated route. Useful if you have no nmea data source.
* source="null://" : no GPS at all
-===Logging tracks===
+===Logging tracks===
To record your trip , you can add a sub-instance "log" to the vehicle. It is possible to add multiple logs.
<source lang="xml">