Doc: Applied title case in section1 titles

Task-number: QTBUG-41250
Change-Id: I788332e3db66e8188fc7d64d1e31995f4b432932
Reviewed-by: Martin Smith <martin.smith@digia.com>
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>

5 files changed, 9 insertions, 9 deletions

diff --git a/src/sensors/doc/src/qtsensorgestures-emulator.qdoc b/src/sensors/doc/src/qtsensorgestures-emulator.qdoc
index ca10035..96232fd 100644
--- a/src/sensors/doc/src/qtsensorgestures-emulator.qdoc
+++ b/src/sensors/doc/src/qtsensorgestures-emulator.qdoc
@@ -34,7 +34,7 @@
 The Emulator can be used for both creating client apps using Qt's built-in sensor gestures,
 and for creating customized recognizers.
 
-\section1 Developing sensor gesture clients.
+\section1 Developing Sensor Gesture Clients
 
 For instance, the Emulator can be used for writing a client app that needs
 to use the "slam" gesture.
diff --git a/src/sensors/doc/src/qtsensors-backend.qdoc b/src/sensors/doc/src/qtsensors-backend.qdoc
index a64b2d1..5047372 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
diff --git a/src/sensors/doc/src/qtsensors-cpp.qdoc b/src/sensors/doc/src/qtsensors-cpp.qdoc
index 583469e..46cb81f 100644
--- a/src/sensors/doc/src/qtsensors-cpp.qdoc
+++ b/src/sensors/doc/src/qtsensors-cpp.qdoc
@@ -81,7 +81,7 @@ Here is an example of creating a sensor on the heap and on the stack.
 
 \snippet sensors/creating.cpp Creating a sensor
 
-\section1 Accessing sensor data in a generic fashion
+\section1 Accessing Sensor Data in a Generic Fashion
 
 The preferred way to deal with sensor data is via the \l{Reading Classes}.
 However, sometimes this may not be possible. For example, you may be deploying
@@ -106,7 +106,7 @@ This code does not require any compile-time links to \l QAccelerometer or
 You can discover all of this information at runtime too. The sensor_explorer example
 shows you information about available sensors.
 
-\section1 Front end, back end
+\section1 Front End, Back End
 
 The Qt Sensors API has a front end, for application developers to use and a back end,
 where device implementors write code to access their hardware. As an application
diff --git a/src/sensors/doc/src/qtsensors.qdoc b/src/sensors/doc/src/qtsensors.qdoc
index 639ca9b..acf7b4f 100644
--- a/src/sensors/doc/src/qtsensors.qdoc
+++ b/src/sensors/doc/src/qtsensors.qdoc
@@ -95,7 +95,7 @@
             \li Information about the Qt SensorGestures C++ API
     \endtable
 
-    \section1 Information for Qt SensorGestures Recognizer Plugin Implementors.
+    \section1 Information for Qt SensorGestures Recognizer Plugin Implementors
 
     \table
         \row
diff --git a/src/sensors/doc/src/qtsensors5.qdoc b/src/sensors/doc/src/qtsensors5.qdoc
index 7e4bf15..3478108 100644
--- a/src/sensors/doc/src/qtsensors5.qdoc
+++ b/src/sensors/doc/src/qtsensors5.qdoc
@@ -62,7 +62,7 @@
 
     The documentation for the module API can be found in SensorGlobal.
 
-    \section1 QML Sensor types
+    \section1 QML Sensor Types
 
     These types represent specific types of sensors.
 
@@ -70,7 +70,7 @@
 
     \annotatedlist qml-sensors_type
 
-    \section1 QML Reading types
+    \section1 QML Reading Types
 
     The data from a sensor comes via a reading class.