Doc: apply title case for section1 qdoc

Task-number: QTBUG-41250
Change-Id: Ia27ca0ce9d0efcc92a48dd40f53b86328796505d
Reviewed-by: Topi Reiniö <topi.reinio@digia.com>

4 files changed, 8 insertions, 8 deletions

diff --git a/doc/src/howtos/exceptionsafety.qdoc b/doc/src/howtos/exceptionsafety.qdoc
index 6a1faaa1..39354974 100644
--- a/doc/src/howtos/exceptionsafety.qdoc
+++ b/doc/src/howtos/exceptionsafety.qdoc
@@ -45,7 +45,7 @@
 
     \tableofcontents
 
-    \section1 Exception safe modules
+    \section1 Exception Safe Modules
 
     \section2 Containers
 
@@ -104,7 +104,7 @@
     create a \l{QImage::isNull()}{null} image if not enough memory exists instead
     of throwing an exception.
 
-    \section1 Recovering from exceptions
+    \section1 Recovering from Exceptions
 
     Currently, the only supported use case for recovering from exceptions thrown
     within Qt (for example due to out of memory) is to exit the event loop and do
@@ -129,7 +129,7 @@
     might already be closed. It is not safe to call a GUI related function
     after catching an exception.
 
-    \section1 Exceptions in client code
+    \section1 Exceptions in Client Code
 
     \section2 Signals and Slots
 
diff --git a/doc/src/howtos/scalabilityintro.qdoc b/doc/src/howtos/scalabilityintro.qdoc
index adffb3b2..7da82782 100644
--- a/doc/src/howtos/scalabilityintro.qdoc
+++ b/doc/src/howtos/scalabilityintro.qdoc
@@ -108,7 +108,7 @@
     of their own, but require you to position their contents. For this, you can
     use Qt Quick Layouts.
 
-    \section1 Laying out Screens Dynamically
+    \section1 Laying Out Screens Dynamically
 
     \l{Qt Quick Layouts} provide ways of laying out screen controls in a row,
     column, or grid, using the RowLayout, ColumnLayout, and GridLayout QML
diff --git a/doc/src/howtos/sharedlibrary.qdoc b/doc/src/howtos/sharedlibrary.qdoc
index 7d1fc53d..e5eac717 100644
--- a/doc/src/howtos/sharedlibrary.qdoc
+++ b/doc/src/howtos/sharedlibrary.qdoc
@@ -134,7 +134,7 @@
     \e{value semantics}, consider using QSharedDataPointer.
 
 
-    \section1  Binary compatibility
+    \section1 Binary Compatibility
 
     For clients loading a shared library, to work correctly, the memory
     layout of the classes being used must match exactly the memory layout of
diff --git a/doc/src/howtos/third-party-libraries.qdoc b/doc/src/howtos/third-party-libraries.qdoc
index 7c1356bc..8ee74fd6 100644
--- a/doc/src/howtos/third-party-libraries.qdoc
+++ b/doc/src/howtos/third-party-libraries.qdoc
@@ -84,7 +84,7 @@
     executable, another library file, etc. The next sections explain the syntax
     with which \c qmake expects you to provide this information.
 
-    \section1 Source code
+    \section1 Source Code
 
     To be able to write
 
@@ -105,7 +105,7 @@
     INCLUDEPATH += 3rdparty/CatWhisperer/include
     \endcode
 
-    \section1 Library files
+    \section1 Library Files
 
     To let \c qmake know where to find the \c CatWhisperer library files,
     use the \l{qmake Variable Reference#LIBS}{LIBS} variable:
@@ -125,7 +125,7 @@
     to specify the \c .lib extension, nor the \c lib prefix
     (on UNIX platforms).
 
-    \section1 Destination directory
+    \section1 Destination Directory
 
     By default, \c qmake creates the executable in the same directory as the
     \c .pro file. We can choose our own directory using the