5 files changed, 21 insertions, 18 deletions
diff --git a/src/dbus/doc/src/dbus-adaptors.qdoc b/src/dbus/doc/src/dbus-adaptors.qdoc
index 3dbedbbcce..e57cc095b9 100644
--- a/src/dbus/doc/src/dbus-adaptors.qdoc
+++ b/src/dbus/doc/src/dbus-adaptors.qdoc
@@ -6,7 +6,7 @@
     \title Using Qt D-Bus Adaptors
     \brief How to create and use DBus adaptors in Qt.
 
-    \ingroup best-practices
+    \ingroup how-to
 
     Adaptors are special classes that are attached to any QObject-derived class
     and provide the interface to the external world using D-Bus. Adaptors are
@@ -44,7 +44,7 @@
       \li \l{Declaring Slots in D-Bus Adaptors}
       \li \l{Declaring Signals in D-Bus Adaptors}
       \li \l{The Qt D-Bus Type System}
-      \li In the \l{D-Bus Complex Ping Pong Example}, \c complexpong.h and
+      \li In the \l{D-Bus Complex Ping Pong} example, \c complexpong.h and
           \c complexpong.cpp show an implementation of QDBusAbstractAdaptor.
     \endlist
 
@@ -87,15 +87,15 @@
 
     Asynchronous slots are marked by the keyword \l Q_NOREPLY in the method
     signature, before the \c void return type and the slot name. The \c quit()
-    slot in the \l {D-Bus Complex Ping Pong Example} is an example of this.
+    slot in the \l {D-Bus Complex Ping Pong} example is an example of this.
 
     \section1 Input-Only Slots
 
     Input-only slots are normal slots that take parameters passed by value or
     by constant reference. However, unlike asynchronous slots, the caller is
     usually waiting for completion of the callee before resuming operation.
-    Therefore, non-asynchronous slots should not block or should state it its
-    documentation that they may do so.
+    Therefore, non-asynchronous slots should not block or should explicitly
+    state it will block in its documentation that they may do so.
 
     Input-only slots have no special marking in their signature, except that
     they take only parameters passed by value or by constant reference.
@@ -193,8 +193,8 @@
     However, signals must still be emitted. The easiest way to emit an adaptor
     signal is to connect another signal to it, so that Qt's signals and slots
     mechanism automatically emits the adaptor signal, too. This can be done in
-    the adaptor's constructor, as you can see in the \l {D-Bus Complex Ping
-    Pong Example}.
+    the adaptor's constructor, as you can see in the \l {D-Bus Complex Ping Pong}
+    example.
 
     The QDBusAbstractAdaptor::setAutoRelaySignals() convenience function can also
     be used to make and break connections between signals in the real object and
diff --git a/src/dbus/doc/src/qt6-changes.qdoc b/src/dbus/doc/src/qt6-changes.qdoc
index c9e73a187a..80cd56c627 100644
--- a/src/dbus/doc/src/qt6-changes.qdoc
+++ b/src/dbus/doc/src/qt6-changes.qdoc
@@ -5,7 +5,7 @@
     \page dbus-changes-qt6.html
     \title Changes to Qt D-Bus
     \ingroup changes-qt-5-to-6
-    \brief Migrate Qt DBus to Qt 6.
+    \brief Minimal porting effort to be able to switch to Qt 6.
 
     Qt 6 is a result of the conscious effort to make the framework more
     efficient and easy to use.
diff --git a/src/dbus/doc/src/qtdbus-cmake.qdoc b/src/dbus/doc/src/qtdbus-cmake.qdoc
index 227642bfb7..86807af6e5 100644
--- a/src/dbus/doc/src/qtdbus-cmake.qdoc
+++ b/src/dbus/doc/src/qtdbus-cmake.qdoc
@@ -4,6 +4,7 @@
 /*!
 \group cmake-commands-qtdbus
 \title CMake Commands in Qt6 DBus
+\brief Lists CMake commands defined in Qt6::DBus.
 
 The following CMake commands are defined when Qt6::DBus is loaded, for instance
 with
@@ -20,7 +21,7 @@ find_package(Qt6 REQUIRED COMPONENTS DBus)
 \ingroup cmake-commands-qtdbus
 
 \title qt_add_dbus_interface
-\target qt6_add_dbus_interface
+\keyword qt6_add_dbus_interface
 
 \summary {Generates C++ sources implementing an interface for a D-Bus interface
 description file.}
@@ -88,7 +89,7 @@ Options can be set using \c set_source_files_properties on the \c dbus_spec:
 \ingroup cmake-commands-qtdbus
 
 \title qt_add_dbus_interfaces
-\target qt6_add_dbus_interfaces
+\keyword qt6_add_dbus_interfaces
 
 \summary {Generates C++ sources implementing interfaces for D-Bus interface
 description files.}
@@ -149,7 +150,7 @@ arguments:
 \ingroup cmake-commands-qtdbus
 
 \title qt_generate_dbus_interface
-\target qt6_generate_dbus_interface
+\keyword qt6_generate_dbus_interface
 
 \summary {Generates a D-Bus interface from a header file.}
 
@@ -171,7 +172,7 @@ qt_generate_dbus_interface(header
 \section1 Description
 
 Parses the C++ source or header file containing a QObject-derived class
-declaration and generates a file containing the D-BUS Introspection XML.
+declaration and generates a file containing the D-Bus Introspection XML.
 
 By default, the generated XML file is stored in the current binary directory,
 and has the same base name as the header. You can specify a different name or
@@ -188,7 +189,7 @@ arguments to the tool can be set after \c{OPTIONS}.
 \ingroup cmake-commands-qtdbus
 
 \title qt_add_dbus_adaptor
-\target qt6_add_dbus_adaptor
+\keyword qt6_add_dbus_adaptor
 
 \summary {Generates an adaptor class for a D-Bus interface.}
 
@@ -246,6 +247,7 @@ argument.
 /*!
 \group cmake-source-file-properties-qtdbus
 \title CMake Source File Properties in Qt6 DBus
+\brief Lists CMake file properties used in Qt6::DBus.
 
 \l{CMake Commands in Qt6 DBus}{CMake Commands} know about the following CMake
 source file properties:
@@ -254,7 +256,7 @@ source file properties:
 */
 
 /*!
-\page cmake-source-file-property-CLASSNAME.html
+\page cmake-source-file-property-classname.html
 \ingroup cmake-source-file-properties-qtdbus
 
 \title CLASSNAME
@@ -271,7 +273,7 @@ with the provided property value.
 */
 
 /*!
-\page cmake-source-file-property-INCLUDE.html
+\page cmake-source-file-property-include.html
 \ingroup cmake-source-file-properties-qtdbus
 
 \title INCLUDE
@@ -288,7 +290,7 @@ to the generated C++ file.
 */
 
 /*!
-\page cmake-source-file-property-NO_NAMESPACE.html
+\page cmake-source-file-property-no-namespace.html
 \ingroup cmake-source-file-properties-qtdbus
 
 \title NO_NAMESPACE
diff --git a/src/dbus/doc/src/qtdbus-module.qdoc b/src/dbus/doc/src/qtdbus-module.qdoc
index 03bba6d952..c89b4dc937 100644
--- a/src/dbus/doc/src/qtdbus-module.qdoc
+++ b/src/dbus/doc/src/qtdbus-module.qdoc
@@ -8,7 +8,7 @@
     to perform Inter-Process Communication using the \l{Qt D-Bus}{D-Bus} protocol.
 
     \ingroup modules
-    \qtcmakepackage Dbus
+    \qtcmakepackage DBus
     \qtvariable dbus
 
     \keyword The QDBus compiler
diff --git a/src/dbus/doc/src/qtdbus-overview.qdoc b/src/dbus/doc/src/qtdbus-overview.qdoc
index b40caf24a6..6342e674fd 100644
--- a/src/dbus/doc/src/qtdbus-overview.qdoc
+++ b/src/dbus/doc/src/qtdbus-overview.qdoc
@@ -5,6 +5,7 @@
     \page qtdbus-overview.html
     \title Qt D-Bus Overview
     \brief Provides insight into the Qt Qt D-Bus module.
+    \ingroup explanations-networkingandconnectivity
 
     D-Bus is an Inter-Process Communication (IPC) and Remote Procedure
     Calling (RPC) mechanism originally developed for Linux to replace
@@ -164,7 +165,7 @@
     This feature can be enabled on a per-application basis by setting the
     \c QDBUS_DEBUG environment variable before running each application.
     For example, we can enable debugging only for the car in the
-    \l{D-Bus Remote Controlled Car Example} by running the controller and the
+    \l{D-Bus Remote Controlled Car} example by running the controller and the
     car in the following way:
 
     \snippet code/doc_src_introtodbus.qdoc QDBUS_DEBUG