Doc: apply title case for section1 qdoc

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

22 files changed, 38 insertions, 38 deletions

diff --git a/doc/src/datastorage.qdoc b/doc/src/datastorage.qdoc
index 648ca12d..782af70b 100644
--- a/doc/src/datastorage.qdoc
+++ b/doc/src/datastorage.qdoc
@@ -49,7 +49,7 @@ from and write to that process.
 \li \l {Serializing Qt Data Types}
 \endlist
 
-\section1 SQL support in Qt
+\section1 SQL Support in Qt
 
 The \l {Qt SQL} module uses driver plugins to communicate with several database
 APIs. Qt has drivers for SQLite, MySQL, DB2, Borland InterBase, Oracle, ODBC,
diff --git a/doc/src/development/qmsdev.qdoc b/doc/src/development/qmsdev.qdoc
index c6ee6a77..8f0028a2 100644
--- a/doc/src/development/qmsdev.qdoc
+++ b/doc/src/development/qmsdev.qdoc
@@ -36,7 +36,7 @@
 
   \tableofcontents
 
-  \section1 How to install the Visual Studio Integration Plugin
+  \section1 How to Install the Visual Studio Integration Plugin
 
   When you install Qt, the integration plugin should be installed for you,
   however, sometimes this does  not happen, so to install the integration
@@ -53,7 +53,7 @@
   work, then contact Qt technical support giving details of
   what went wrong.
 
-  \section1 How to uninstall the Visual Studio Integration Plugin
+  \section1 How to Uninstall the Visual Studio Integration Plugin
 
   When you want to uninstall the integration plugin, just carry out the
   following steps.
@@ -63,7 +63,7 @@
   \li Delete the file '%MSDevDir%\\addins\\qmsdev.dll'
   \endlist
 
-  \section1 What can the Visual Studio Integration Plugin do?
+  \section1 What Can the Visual Studio Integration Plugin Do?
 
   The integration plugin adds the following options to Visual Studio:
 
diff --git a/doc/src/frameworks-technologies/threads.qdoc b/doc/src/frameworks-technologies/threads.qdoc
index 8a0c567d..64b6fa0c 100644
--- a/doc/src/frameworks-technologies/threads.qdoc
+++ b/doc/src/frameworks-technologies/threads.qdoc
@@ -788,7 +788,7 @@
     create a copy of the document, and pass the copy to another thread for
     further processing (such as printing).
 
-    \section1 Threads and the SVG module
+    \section1 Threads and the SVG Module
 
     The QSvgGenerator and QSvgRenderer classes in the QtSvg module
     are reentrant.
diff --git a/doc/src/frameworks-technologies/why-moc.qdoc b/doc/src/frameworks-technologies/why-moc.qdoc
index 812f90e1..ba3339e7 100644
--- a/doc/src/frameworks-technologies/why-moc.qdoc
+++ b/doc/src/frameworks-technologies/why-moc.qdoc
@@ -52,7 +52,7 @@
 
     Here are some reasons why Qt uses the moc:
 
-    \section1 Syntax matters
+    \section1 Syntax Matters
 
     Syntax isn't just sugar: the syntax we use to express our algorithms can
     significantly affect the readability and maintainability of our code.
diff --git a/doc/src/getting-started/installation.qdoc b/doc/src/getting-started/installation.qdoc
index 7fa1bb5b..00cdfec4 100644
--- a/doc/src/getting-started/installation.qdoc
+++ b/doc/src/getting-started/installation.qdoc
@@ -110,7 +110,7 @@ visit the following page:
 \endlist
 
 \target openssl-v1later
-\section1 OpenSSL (version 1.0.0 or later)
+\section1 OpenSSL (Version 1.0.0 or Later)
 
 Support for \l{SSL}{Secure Sockets Layer (SSL)} communication is provided by the
 \l{OpenSSL Toolkit}, which must be obtained separately.
@@ -133,13 +133,13 @@ More information about enabling SSL support can be found in the
 Qt for Windows CE has some requirements that are given in more detail
 in the \l{Qt for Windows CE Requirements} document.
 
-\section1 Step 1: Install the License File (commercial editions only)
+\section1 Step 1: Install the License File (Commercial Editions Only)
     Uncompress the files to the directory where you want to build;
     e.g., \c{C:\Qt\%VERSION%}.
 
     \note The install path must not contain any spaces.
 
-\section1 Step 2: Set the Environment variables
+\section1 Step 2: Set the Environment Variables
 
     In order to build and use Qt, the \c PATH environment variable needs
     to be extended:
diff --git a/doc/src/graphics.qdoc b/doc/src/graphics.qdoc
index 6c2195a4..220ca02f 100644
--- a/doc/src/graphics.qdoc
+++ b/doc/src/graphics.qdoc
@@ -37,7 +37,7 @@ loading and saving of various image formats.
 
 
 
-\section1 2D graphics with QPainter
+\section1 2D Graphics with QPainter
 
 QPainter provides API for drawing vector graphics, text and images
 onto different surfaces, or QPaintDevice instances, such as QImage,
@@ -131,7 +131,7 @@ prefer the ones starting with \c QOpenGL.
 
 
 
-\section1 Qt Quick scene graph
+\section1 Qt Quick Scene Graph
 
 Qt Quick 2 introduces an OpenGL (ES) 2.0 scene graph for
 rendering. It generally improves the performance of Qt Quick 2
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
diff --git a/doc/src/platforms/blackberry.qdoc b/doc/src/platforms/blackberry.qdoc
index 4296291e..6e458932 100644
--- a/doc/src/platforms/blackberry.qdoc
+++ b/doc/src/platforms/blackberry.qdoc
@@ -313,7 +313,7 @@
     You may now either move on to building your applications or continue here to install
     some additional git submodules to gain access to additional features of Qt 5.
 
-    \section1 Building other Modules
+    \section1 Building Other Modules
 
     If you want to build additional git submodules, make sure to do this in the right order,
     because some git submodules depend on each other.
diff --git a/doc/src/platforms/linux.qdoc b/doc/src/platforms/linux.qdoc
index 62dfad90..41589ab6 100644
--- a/doc/src/platforms/linux.qdoc
+++ b/doc/src/platforms/linux.qdoc
@@ -122,7 +122,7 @@
     \title Qt for X11 Requirements
     \brief Setting up the X11 environment for Qt.
 
-    \section1 Platform plugin dependencies
+    \section1 Platform Plugin Dependencies
 
     On Linux, the \e xcb QPA (Qt Platform Abstraction) platform plugin is used.
     It provides the basic functionality needed by \l{Qt GUI} and \l{Qt Widgets}
@@ -376,7 +376,7 @@
     Qt for X11 has some requirements that are given in more detail
     in the \l{Qt for X11 Requirements} document.
 
-    \section1 Step 1: Installing the License File (commercial editions only)
+    \section1 Step 1: Installing the License File (Commercial Editions Only)
         If you have the commercial edition of Qt, install your license
         file as \c{$HOME/.qt-license}.
 
diff --git a/doc/src/platforms/osx.qdoc b/doc/src/platforms/osx.qdoc
index e444b7b5..3fc76d59 100644
--- a/doc/src/platforms/osx.qdoc
+++ b/doc/src/platforms/osx.qdoc
@@ -206,7 +206,7 @@
     \l{http://openradar.appspot.com/7214991}
     {iPhone simulator conflicts with the package installer}.
 
-    \section1 Step 1: Install the License File (commercial editions only)
+    \section1 Step 1: Install the License File (Commercial Editions Only)
         If you have the commercial edition of Qt, install your license
         file as \c{$HOME/.qt-license}.
 
@@ -221,7 +221,7 @@
         This creates the directory \c{/tmp/qt-everywhere-opensource-src-%VERSION%}
         containing the files from the archive.
 
-    \section1 Step 2:  Build the Qt Library
+    \section1 Step 2: Build the Qt Library
 
         To configure the Qt library for your machine type, run the
         \c{./configure} script in the package directory.
@@ -267,7 +267,7 @@
         removed by entering the build directory and typing \c{make confclean}
         before running \c configure again.
 
-    \section1 Step 3: Set the Environment variables
+    \section1 Step 3: Set the Environment Variables
 
         In order to use Qt, some environment variables need to be
         extended.
diff --git a/doc/src/platforms/wince-introduction.qdoc b/doc/src/platforms/wince-introduction.qdoc
index ed511bec..e88faca5 100644
--- a/doc/src/platforms/wince-introduction.qdoc
+++ b/doc/src/platforms/wince-introduction.qdoc
@@ -65,7 +65,7 @@
 
     \tableofcontents
 
-    \section1 Required tools
+    \section1 Required Tools
 
     In order to use Qt for Windows CE you need to have Visual Studio
     2005 or 2008 and at least one of the supported Windows
@@ -78,7 +78,7 @@
 
     Follow the instructions found in \l{Installing Qt for Windows CE}.
 
-    \section1 Building your own applications
+    \section1 Building Your Own Applications
 
     If you are new to Qt development, have a look at \l{Qt Overviews}
     and \l{Qt Examples And Tutorials}{Tutorials}. In general there is
@@ -92,7 +92,7 @@
     For more information on how to use qmake have a look at the \l
     {Getting Started}{qmake Tutorial}.
 
-    \section1 Running the application
+    \section1 Running the Application
 
     In order to run the application, it needs to be deployed on the
     Windows CE/Mobile device you want to test it for. This can either
diff --git a/doc/src/platforms/windows.qdoc b/doc/src/platforms/windows.qdoc
index c0faa3e6..d03353cf 100644
--- a/doc/src/platforms/windows.qdoc
+++ b/doc/src/platforms/windows.qdoc
@@ -928,7 +928,7 @@ Arguments:
     more information, visit the \l{Getting Started with Qt} page.
 
 
-    \section1 Step 1: Install the License File (commercial editions only)
+    \section1 Step 1: Install the License File (Commercial Editions Only)
 
         If you have the commercial edition of Qt, copy the license file
         from your account on the distribution server into your home directory
@@ -948,7 +948,7 @@ Arguments:
         \note The install path must not contain any spaces or Windows specific
         file system characters.
 
-    \section1 Step 3: Set the Environment variables
+    \section1 Step 3: Set the Environment Variables
 
         We recommend creating a desktop link that opens a command
         prompt with the environment set up similar to the
diff --git a/doc/src/platforms/winrt.qdoc b/doc/src/platforms/winrt.qdoc
index d0a8d3b5..c65c65a7 100644
--- a/doc/src/platforms/winrt.qdoc
+++ b/doc/src/platforms/winrt.qdoc
@@ -116,7 +116,7 @@
 
     \note Remote PCs, such as the Surface, are not yet supported for deployment by Creator.
 
-    \section1 Building from source
+    \section1 Building from Source
 
     We assume that you have cloned the Qt 5 repositories (or obtained
     the Qt sources elsewhere) and followed the platform-independent
diff --git a/doc/src/portingcppapps_toqt5.qdoc b/doc/src/portingcppapps_toqt5.qdoc
index 7fa059cd..308eda9f 100644
--- a/doc/src/portingcppapps_toqt5.qdoc
+++ b/doc/src/portingcppapps_toqt5.qdoc
@@ -61,7 +61,7 @@ step-by-step instructions take you through the changes required to achieve this:
    \li Save changes and run your application.
 \endlist
 
-\section1 Related topics
+\section1 Related Topics
 \list
 \li \l {C++ API Changes}
 \li \l {Porting QML Applications to Qt 5 Example}
diff --git a/doc/src/qmlapp/internationalization.qdoc b/doc/src/qmlapp/internationalization.qdoc
index 335f23ad..dd6b823d 100644
--- a/doc/src/qmlapp/internationalization.qdoc
+++ b/doc/src/qmlapp/internationalization.qdoc
@@ -30,7 +30,7 @@
 \title Internationalization and Localization with Qt Quick
 \brief Following these steps, you can write your Qt Quick application so it can be localized for multiple languages
 
-\section1 Internationalizing your Application
+\section1 Internationalizing Your Application
 
 The following sections describe various aspects of internationalizing your QML
 source code. If you follow these guides for all the user interface components in
@@ -227,7 +227,7 @@ Component.onCompleted: {
 }
 \endcode
 
-\section1 Localizing your Application
+\section1 Localizing Your Application
 
 Qt Quick applications use the same underlying localization system as Qt C++
 applications (lupdate, lrelease and .ts files). You use the same tools as
diff --git a/doc/src/qmlapp/porting.qdoc b/doc/src/qmlapp/porting.qdoc
index daf122ae..5edcd704 100644
--- a/doc/src/qmlapp/porting.qdoc
+++ b/doc/src/qmlapp/porting.qdoc
@@ -38,7 +38,7 @@ This article describes the changes that affect your existing code. If you are
 interested in the summary of all new features in Qt 5 for QML application development, see
 \l{Qt QML Release Notes} and \l{Qt Quick Release Notes}.
 
-\section1 QML Language changes
+\section1 QML Language Changes
 
 There are very few changes in the QML language that affect the porting of existing Qt 4.8 QML code to Qt 5. These are:
 
diff --git a/doc/src/qmlapp/qtquicktest.qdoc b/doc/src/qmlapp/qtquicktest.qdoc
index 184d9dac..5e8ae3b8 100644
--- a/doc/src/qmlapp/qtquicktest.qdoc
+++ b/doc/src/qmlapp/qtquicktest.qdoc
@@ -57,7 +57,7 @@
     to be executed. See the documentation for the \l {QtTest::TestCase}{TestCase} and
     \l {QtTest::SignalSpy}{SignalSpy} types for more information on writing test cases.
 
-    \section1 Running tests
+    \section1 Running Tests
 
     Test cases are launched by a C++ harness that consists of
     the following code:
diff --git a/doc/src/qmlapp/usecases/integratingjs.qdoc b/doc/src/qmlapp/usecases/integratingjs.qdoc
index b278bc93..bc0554e3 100644
--- a/doc/src/qmlapp/usecases/integratingjs.qdoc
+++ b/doc/src/qmlapp/usecases/integratingjs.qdoc
@@ -52,7 +52,7 @@ using the item id.
 
 \snippet qmlapp/usecases/integratingjs-inline.qml 0
 
-\section1 Using JavaScript files
+\section1 Using JavaScript Files
 
 JavaScript files can be used for abstracting out logic from QML files. To do this, first place your functions inside a
 .js file like in the example shown.
diff --git a/doc/src/qmlapp/usecases/text.qdoc b/doc/src/qmlapp/usecases/text.qdoc
index b72754b7..2a8a01e8 100644
--- a/doc/src/qmlapp/usecases/text.qdoc
+++ b/doc/src/qmlapp/usecases/text.qdoc
@@ -43,7 +43,7 @@ Rich text like markup can be used to selectively style specific sections of text
 Text::textFormat to Text.StyledText to use this functionality. More details are available in the documentation of the
 \l{Text} type.
 
-\section1 Laying out Text
+\section1 Laying Out Text
 
 By default, Text will display the text as a single line unless it contains embedded newlines. To wrap the line, set the
 wrapMode property and give the text an explicit width for it to wrap to. If the width or height is not explicitly set,