summaryrefslogtreecommitdiffstats
path: root/src/sensors/doc/src/qtsensors-backend.qdoc
diff options
context:
space:
mode:
authorNico Vertriest <nico.vertriest@digia.com>2014-10-07 14:02:04 +0200
committerNico Vertriest <nico.vertriest@digia.com>2014-10-09 12:58:21 +0200
commitff98a9a27a18e6a48afa705e5cd84bd9461ad554 (patch)
tree5d60e80e3550a1a69b2270d35c56f4e3248307ee /src/sensors/doc/src/qtsensors-backend.qdoc
parent4756a79d456d2fdd7aa1e5cb562a50165daf3d7f (diff)
Doc: Applied title case in section1 titlesv5.4.0-rc1v5.4.0-beta1
Task-number: QTBUG-41250 Change-Id: I788332e3db66e8188fc7d64d1e31995f4b432932 Reviewed-by: Martin Smith <martin.smith@digia.com> Reviewed-by: Topi Reiniƶ <topi.reinio@digia.com>
Diffstat (limited to 'src/sensors/doc/src/qtsensors-backend.qdoc')
-rw-r--r--src/sensors/doc/src/qtsensors-backend.qdoc6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/sensors/doc/src/qtsensors-backend.qdoc b/src/sensors/doc/src/qtsensors-backend.qdoc
index a64b2d1f..50473725 100644
--- a/src/sensors/doc/src/qtsensors-backend.qdoc
+++ b/src/sensors/doc/src/qtsensors-backend.qdoc
@@ -62,7 +62,7 @@ classes to use.
\title Creating a sensor plugin
\ingroup sensors_backend_topics
-\section1 How a sensor plugin is loaded
+\section1 How a Sensor Plugin is Loaded
Since sensor backends are created on demand, the sensor plugin is loaded and asked
to register the sensor backends it handles. The plugin should implement
@@ -85,7 +85,7 @@ An example follows.
\title Determining the default sensor for a type
\ingroup sensors_backend_topics
-\section1 Multiple sensors can exist for a type
+\section1 Multiple Sensors Can Exist for a Type
Sensors was designed so that multiple sensors could exist for a given type. Why?
Consider this example.
@@ -94,7 +94,7 @@ The N900 has an accelerometer built-in. It also features bluetooth and can pair
with a gaming controller that features an accelerometer. To a developer writing
a game these two devices are conceptually the same type.
-\section1 Default sensor for a type
+\section1 Default Sensor for a Type
To avoid the need to know (or check) what the default sensor for a type is, the
system will use the default sensor for a type. Most of the time this is what the