summaryrefslogtreecommitdiff
path: root/src/positioning/doc/src/qml-position.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'src/positioning/doc/src/qml-position.qdoc')
-rw-r--r--src/positioning/doc/src/qml-position.qdoc10
1 files changed, 5 insertions, 5 deletions
diff --git a/src/positioning/doc/src/qml-position.qdoc b/src/positioning/doc/src/qml-position.qdoc
index 3f112b79..27e55583 100644
--- a/src/positioning/doc/src/qml-position.qdoc
+++ b/src/positioning/doc/src/qml-position.qdoc
@@ -71,7 +71,7 @@ The \l {coordinate} is a basic unit of geographical information. The
The three dimensional position of an object such as a mobile device can be specified by giving
the latitude, longitude and altitude. That is the values held in the
-l\ {coordinate} type. Additionally for computation of future
+\l {coordinate} type. Additionally for computation of future
positions we would like to know if the object is moving, what \l [QML] {Position::}{speed} it is
doing and what is the \l {Position::timestamp}{timestamp} of the last position data. Position
therefore includes values for the \l {Position::coordinate}{coordinate},
@@ -85,10 +85,10 @@ the \l {Position::latitudeValid}{latitudeValid}, \l {Position::longitudeValid}{l
\section2 PositionSource Type
-We have a Position type, a \l {coordinate} type but where does the data come from?
-Also it is a good idea to be able to indicate alternative sources.
-Perhaps instead of directly picking up GPS satellites it might be desirable to do
-some testing using a datafile.
+We have a \l Position type, a \l {coordinate} type but where does the data come
+from? Also it is a good idea to be able to indicate alternative sources.
+Perhaps instead of directly picking up GPS satellites it might be desirable to
+do some testing using a datafile.
The \l PositionSource type provides the developer with control, within the
limits allowed by the platform, of the source of the geographical data.