Documentation: Fix inconsistent section levels in class descriptions

They cause warnings when generating Qt for Python documentation.

Pick-to: 6.12
Change-Id: If09df5b2523b3097ed9ce9253d46b3f4cf5ce60c
Reviewed-by: Paul Wicking <paul.wicking@qt.io>

4 files changed, 8 insertions, 9 deletions

diff --git a/src/qml/qml/qqmlcomponent.cpp b/src/qml/qml/qqmlcomponent.cpp
index 0058406ff6..a0e58a9345 100644
--- a/src/qml/qml/qqmlcomponent.cpp
+++ b/src/qml/qml/qqmlcomponent.cpp
@@ -115,7 +115,7 @@ V4_DEFINE_EXTENSION(QQmlComponentExtension, componentExtension);
     constructor of a QObject subclass, as the instance will not yet have
     a context nor engine.
 
-    \section2 Network Components
+    \section1 Network Components
 
     If the URL passed to QQmlComponent is a network resource, or if the QML document references a
     network resource, the QQmlComponent has to fetch the network data before it is able to create
@@ -202,7 +202,7 @@ V4_DEFINE_EXTENSION(QQmlComponentExtension, componentExtension);
     property or use it in a type annotation. If you need this, prefer using
     \l{Defining Object Types through QML Documents#Inline Components}{inline components}.
 
-    \section2 Creation Context
+    \section1 Creation Context
 
     The creation context of a Component corresponds to the context where the Component was declared.
     This context is used as the parent context (creating a \l{qtqml-documents-scope.html#component-instance-hierarchy}{context hierarchy})
diff --git a/src/qml/qml/qqmlcontext.cpp b/src/qml/qml/qqmlcontext.cpp
index 693457e96a..7df8818652 100644
--- a/src/qml/qml/qqmlcontext.cpp
+++ b/src/qml/qml/qqmlcontext.cpp
@@ -33,7 +33,7 @@ QT_BEGIN_NAMESPACE
     explicitly. The simplest way to ensure this is to give the QQmlContext a
     \l{QObject::setParent()}{parent}.
 
-    \section2 The Context Hierarchy
+    \section1 The Context Hierarchy
 
     Contexts form a hierarchy. The root of this hierarchy is the QML engine's
     \l {QQmlEngine::rootContext()}{root context}. Each QML component creates its
@@ -44,7 +44,7 @@ QT_BEGIN_NAMESPACE
     context, their bindings are.  If a context is destroyed, the property bindings of
     outstanding QML objects will stop evaluating.
 
-    \section2 Context Properties
+    \section1 Context Properties
 
     Contexts also allow data to be exposed to the QML components instantiated
     by the QML engine. Such data is invisible to any tooling, including the
diff --git a/src/quick/items/qquickrhiitem.cpp b/src/quick/items/qquickrhiitem.cpp
index 1fd4234f31..9184b1493c 100644
--- a/src/quick/items/qquickrhiitem.cpp
+++ b/src/quick/items/qquickrhiitem.cpp
@@ -100,7 +100,7 @@ QT_BEGIN_NAMESPACE
     initialized, and all QQuickRhiItem instances in the scene will render using
     the same 3D API.
 
-    \section2 A simple example
+    \section1 A simple example
 
     Take the following subclass of QQuickRhiItem. It is shown here in complete
     form. It renders a single triangle with a perspective projection, where the
diff --git a/src/quick/util/qquickimageprovider.cpp b/src/quick/util/qquickimageprovider.cpp
index e52d8e7232..7720818304 100644
--- a/src/quick/util/qquickimageprovider.cpp
+++ b/src/quick/util/qquickimageprovider.cpp
@@ -226,7 +226,7 @@ void QQuickImageResponse::cancel()
     If you want the rest of the URL to be case insensitive, you will have to take care
     of that yourself inside your image provider.
 
-    \section2 An Example
+    \section1 An Example
 
     Here are two images. Their \c source values indicate they should be loaded by
     an image provider named "colors", and the images to be loaded are "yellow"
@@ -263,8 +263,7 @@ void QQuickImageResponse::cancel()
 
     It is possible to provide \l {High Resolution Versions of Images}{"@nx" high DPI syntax}.
 
-
-    \section2 Asynchronous Image Loading
+    \section1 Asynchronous Image Loading
 
     Image providers that support QImage or Texture loading automatically include support
     for asychronous loading of images. To enable asynchronous loading for an
@@ -293,7 +292,7 @@ void QQuickImageResponse::cancel()
     See the \l {imageresponseprovider}{Image Response Provider Example} for a complete implementation.
 
 
-    \section2 Image Caching
+    \section1 Image Caching
 
     Images returned by a QQuickImageProvider are automatically cached,
     similar to any image loaded by the QML engine. When an image with a