summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
-rw-r--r--doc/src/extras-changes.qdoc2
-rw-r--r--doc/src/howtos/installer-cli.qdoc4
-rw-r--r--doc/src/platforms/emb-linux.qdoc2
-rw-r--r--doc/src/platforms/vxworks.qdoc6
4 files changed, 7 insertions, 7 deletions
diff --git a/doc/src/extras-changes.qdoc b/doc/src/extras-changes.qdoc
index c8a782600..869f1568f 100644
--- a/doc/src/extras-changes.qdoc
+++ b/doc/src/extras-changes.qdoc
@@ -155,7 +155,7 @@
The \l {Application Permissions} infrastructure allows requesting a set of
permissions in a cross-platform manner.
- The \l {QtAndroidPrivate Namespace} can be used to access Android-specific
+ The \l QtAndroidPrivate namespace can be used to access Android-specific
permissions not covered by the cross-platform permissions system.
*/
diff --git a/doc/src/howtos/installer-cli.qdoc b/doc/src/howtos/installer-cli.qdoc
index 5a72758b2..d0fb27b10 100644
--- a/doc/src/howtos/installer-cli.qdoc
+++ b/doc/src/howtos/installer-cli.qdoc
@@ -289,7 +289,7 @@
\li In case you want different answers to certain queries, you can use
this option. For example,
\c{--auto-answer telemetry-question=Yes,AssociateCommonFiletypes=Yes}.
- See all message identifiers in \l{Message Identifiers for --auto-answer}.
+ See all message identifiers in \l{Message Identifiers for \--auto-answer}.
\row
\li \c{--accept-messages}
\li Accepts all message queries.
@@ -320,7 +320,7 @@
question and message type. You can pick up the identifiers from there.
\endtable
- \section2 Message Identifiers for --auto-answer
+ \section2 Message Identifiers for \--auto-answer
Use the \c{--auto-answer} option to provide answers to certain queries. The
following table lists known identifiers and values used for
diff --git a/doc/src/platforms/emb-linux.qdoc b/doc/src/platforms/emb-linux.qdoc
index c939d868f..0fd606812 100644
--- a/doc/src/platforms/emb-linux.qdoc
+++ b/doc/src/platforms/emb-linux.qdoc
@@ -254,7 +254,7 @@
only supported QWindow surface type is QSurface::VulkanSurface. For Qt Quick
applications this implies that Vulkan-based rendering must be enforced either
by setting \c{QSG_RHI_BACKEND=vulkan} in the environment, or by calling
- \l{QQuickWindow::setGraphicsApi(QSGRendererInterface::Vulkan);} early on
+ \l{QQuickWindow::setGraphicsApi}(QSGRendererInterface::Vulkan); early on
before creating a QQuickWindow or QQuickView.
To use this platform plugin, run the application with \c{-platform vkkhrdisplay}
diff --git a/doc/src/platforms/vxworks.qdoc b/doc/src/platforms/vxworks.qdoc
index 2655800d6..a1352cda3 100644
--- a/doc/src/platforms/vxworks.qdoc
+++ b/doc/src/platforms/vxworks.qdoc
@@ -57,7 +57,7 @@
\li \l {Qt Network}
\li
\row
- \li \l {Qt QML}
+ \li \l {Qt Qml}
\li
\row
\li \l {Qt Quick}
@@ -92,7 +92,7 @@
\li \l {Qt Concurrent}
\li
\row
- \li \l {Qt GRPC/Protobuf}
+ \li \l {Qt GRPC}{Qt GRPC/Protobuf}
\li
\row
\li \l {Qt Graphs}
@@ -104,7 +104,7 @@
\li \l {Qt Multimedia}
\li
\row
- \li \l {Qt Native Interfaces}
+ \li \l {Native Interfaces}{Qt Native Interfaces}
\li
\row
\li \l {Qt OpenGL}