Doc: Use title case in section1 titles

Using Python script title-cased.py

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

7 files changed, 25 insertions, 25 deletions

diff --git a/src/widgets/doc/src/model-view-programming.qdoc b/src/widgets/doc/src/model-view-programming.qdoc
index 3a8fd54bcf..8978efa1e3 100644
--- a/src/widgets/doc/src/model-view-programming.qdoc
+++ b/src/widgets/doc/src/model-view-programming.qdoc
@@ -214,7 +214,7 @@
     classes, such as QListView, QTableView, and QTreeView with
     QStandardItemModel.
 
-    \section1 Using models and views
+    \section1 Using Models and Views
 
     The following sections explain how to use the model/view pattern
     in Qt. Each section includes an example and is followed by a
@@ -282,7 +282,7 @@
     of items. This subject is covered in more detail in the section about
     \l{Handling Selections in Item Views}.
 
-    \section1 Model classes
+    \section1 Model Classes
 
     Before examining how selections are handled, you may find it
     useful to examine the concepts used in the model/view framework.
@@ -518,7 +518,7 @@
     section, we demonstrate this by creating a convenient ready-to-use
     model for holding lists of strings.
 
-    \section1 View classes
+    \section1 View Classes
 
     \section2 Concepts
 
@@ -678,7 +678,7 @@
     each view; for example, a contiguous selection in a table view can be
     represented as a fragmented set of highlighted items in a tree view.
 
-    \section1 Delegate classes
+    \section1 Delegate Classes
 
     \section2 Concepts
 
@@ -863,7 +863,7 @@
     be less integrated into applications, and will be less usable than
     those that emit hints to support common editing actions.
 
-    \section1 Handling selections in item views
+    \section1 Handling Selections in Item Views
 
     \section2 Concepts
 
@@ -1139,7 +1139,7 @@
     determine whether any given item is the parent of another level of
     items.
 
-    \section1 Creating new models
+    \section1 Creating New Models
 
     The separation of functionality between the model/view components allows
     models to be created that can take advantage of existing views. This
@@ -1405,7 +1405,7 @@
     virtual functions that must be implemented to enable various features in
     different types of models.
 
-    \section1 Item view convenience classes
+    \section1 Item View Convenience Classes
 
     The item-based widgets have names which reflect their uses:
     \c QListWidget provides a list of items, \c QTreeWidget displays a
@@ -1832,7 +1832,7 @@
 
     \sa {itemviews/puzzle}{Item Views Puzzle Example}
 
-    \section1 Proxy models
+    \section1 Proxy Models
 
     In the model/view framework, items of data supplied by a single model can be shared
     by any number of views, and each of these can possibly represent the same information
@@ -1917,7 +1917,7 @@
     \l{QSortFilterProxyModel::lessThan()}{lessThan()} function to perform custom
     comparisons.
 
-    \section1 Model subclassing reference
+    \section1 Model Subclassing Reference
 
     Model subclasses need to provide implementations of many of the virtual functions
     defined in the QAbstractItemModel base class. The number of these functions that need
@@ -2299,7 +2299,7 @@
     false and does nothing.
 
     \keyword Model/View Classes
-    \section1 The model/view classes
+    \section1 The Model/View Classes
 
     These classes use the model/view design pattern in which the
     underlying data (in the model) is kept separate from the way the
@@ -2307,7 +2307,7 @@
 
     \annotatedlist model-view
 
-    \section1 Related examples
+    \section1 Related Examples
 
     \list
     \li \l{itemviews/dirview}{Dir View}
diff --git a/src/widgets/doc/src/widgets-and-layouts/styles.qdoc b/src/widgets/doc/src/widgets-and-layouts/styles.qdoc
index f8b3d80b67..042a0c9f14 100644
--- a/src/widgets/doc/src/widgets-and-layouts/styles.qdoc
+++ b/src/widgets/doc/src/widgets-and-layouts/styles.qdoc
@@ -84,7 +84,7 @@
 
     \annotatedlist appearance
 
-    \section1 The QStyle implementation
+    \section1 The QStyle Implementation
 
     The API of QStyle contains functions that draw the widgets, static
     helper functions to do common and difficult tasks (e.g.,
diff --git a/src/widgets/doc/src/widgets-and-layouts/stylesheet.qdoc b/src/widgets/doc/src/widgets-and-layouts/stylesheet.qdoc
index 48e3478130..9f22ee1540 100644
--- a/src/widgets/doc/src/widgets-and-layouts/stylesheet.qdoc
+++ b/src/widgets/doc/src/widgets-and-layouts/stylesheet.qdoc
@@ -512,7 +512,7 @@
     In contrast, setting a font and propagate using QWidget::setFont() and
     QWidget::setPalette() propagates to child widgets.
 
-    \section1 Widgets inside C++ namespaces
+    \section1 Widgets Inside C++ Namespaces
 
     The Type Selector can be used to style widgets of a particular type. For
     example,
@@ -528,7 +528,7 @@
 
     \snippet code/doc_src_stylesheet.cpp 27
 
-    \section1 Setting QObject properties
+    \section1 Setting QObject Properties
 
     From 4.3 and above, any designable Q_PROPERTY
     can be set using the qproperty-<property name> syntax.
@@ -3549,7 +3549,7 @@
     [Hint: The \l{The Style Sheet Syntax#Conflict Resolution}{Conflict Resolution} section above explains
     what happens in cases like this.]
 
-    \section1 Customizing specific widgets
+    \section1 Customizing Specific Widgets
 
     This section provides examples to customize specific widgets using Style Sheets.
 
@@ -3930,7 +3930,7 @@
     \sa {Style Sheet Example}, {Supported HTML Subset}, QStyle
 
 
-    \section1 Common mistakes
+    \section1 Common Mistakes
 
     This section lists some common mistakes when using stylesheets.
 
diff --git a/src/widgets/doc/src/widgets-tutorial.qdoc b/src/widgets/doc/src/widgets-tutorial.qdoc
index 0a80a976b9..3e65d3e22d 100644
--- a/src/widgets/doc/src/widgets-tutorial.qdoc
+++ b/src/widgets/doc/src/widgets-tutorial.qdoc
@@ -54,7 +54,7 @@
     This means that when you delete a window widget, all the child
     widgets it contains are also deleted.
 
-    \section1 Writing a main Function
+    \section1 Writing a Main Function
 
     Many of the GUI examples provided with Qt follow the pattern of
     having a \c{main.cpp} file, which contains the standard code to
@@ -72,7 +72,7 @@
     function returns. Finally, \c{main()} returns the value returned
     by QApplication::exec().
 
-    \section1 Simple widget examples
+    \section1 Simple Widget Examples
 
     Each of theses simple widget examples is written entirely within
     the \c main() function.
@@ -87,7 +87,7 @@
     \li \l {tutorials/widgets/nestedlayouts} {Nested layouts}
     \endlist
 
-    \section1 Real world widget examples
+    \section1 Real World Widget Examples
 
     In these \l{Qt Widgets Examples} {more advanced examples}, the code
     that creates the widgets and layouts is stored in other files. For
diff --git a/src/widgets/graphicsview/qgraphicsanchorlayout.cpp b/src/widgets/graphicsview/qgraphicsanchorlayout.cpp
index 99d20c2aad..a7e0e71f15 100644
--- a/src/widgets/graphicsview/qgraphicsanchorlayout.cpp
+++ b/src/widgets/graphicsview/qgraphicsanchorlayout.cpp
@@ -92,7 +92,7 @@
     If the spacing is negative, the items will overlap to some extent.
 
 
-    \section1 Known issues
+    \section1 Known Issues
     There are some features that QGraphicsAnchorLayout currently does not support.
     This might change in the future, so avoid using these features if you want to
     avoid any future regressions in behaviour:
diff --git a/src/widgets/kernel/qopenglwidget.cpp b/src/widgets/kernel/qopenglwidget.cpp
index de402cdb7d..543f59d7d1 100644
--- a/src/widgets/kernel/qopenglwidget.cpp
+++ b/src/widgets/kernel/qopenglwidget.cpp
@@ -149,7 +149,7 @@ QT_BEGIN_NAMESPACE
 
   \endlist
 
-  \section1 OpenGL function calls, headers and QOpenGLFunctions
+  \section1 OpenGL Function Calls, Headers and QOpenGLFunctions
 
   When making OpenGL function calls, it is strongly recommended to avoid calling
   the functions directly. Instead, prefer using QOpenGLFunctions (when making
@@ -177,7 +177,7 @@ QT_BEGIN_NAMESPACE
   feasible. This means that constants and function pointer typedefs from ARB,
   EXT, OES extensions are automatically available.
 
-  \section1 Code examples
+  \section1 Code Examples
 
   To get started, the simplest QOpenGLWidget subclass could like like the following:
 
@@ -282,7 +282,7 @@ QT_BEGIN_NAMESPACE
   fully controlled by the thread, e.g. an additional framebuffer object, and
   blitting to the QOpenGLWidget's framebuffer at a suitable time.
 
-  \section1 Context sharing
+  \section1 Context Sharing
 
   When multiple QOpenGLWidgets are added as children to the same top-level
   widget, their contexts will share with each other. This does not apply for
@@ -311,7 +311,7 @@ QT_BEGIN_NAMESPACE
   created later. Some other drivers may behave in unexpected ways when trying to
   utilize shared resources between different threads.
 
-  \section1 Resource initialization and cleanup
+  \section1 Resource Initialization and Cleanup
 
   The QOpenGLWidget's associated OpenGL context is guaranteed to be current
   whenever initializeGL() and paintGL() are invoked. Do not attempt to create
diff --git a/src/widgets/widgets/qmenu.cpp b/src/widgets/widgets/qmenu.cpp
index a0d3077a79..f2aefe6ea9 100644
--- a/src/widgets/widgets/qmenu.cpp
+++ b/src/widgets/widgets/qmenu.cpp
@@ -1304,7 +1304,7 @@ void QMenu::initStyleOption(QStyleOptionMenuItem *option, const QAction *action)
     do not support the signals: aboutToHide (), aboutToShow () and hovered ().
     It is not possible to display an icon in a native menu on Windows Mobile.
 
-    \section1 QMenu on Mac OS X with Qt build against Cocoa
+    \section1 QMenu on Mac OS X with Qt Build Against Cocoa
 
     QMenu can be inserted only once in a menu/menubar. Subsequent insertions will
     have no effect or will result in a disabled menu item.