diff --git a/examples/webengine/customdialogs/doc/src/customdialogs.qdoc b/examples/webengine/customdialogs/doc/src/customdialogs.qdoc
index 3fc888a777a4819a9787c45d5cc5837997d4ab5f..5c550ed5eb1baaa93d50de4a94fdafd24589cc79 100644
--- a/examples/webengine/customdialogs/doc/src/customdialogs.qdoc
+++ b/examples/webengine/customdialogs/doc/src/customdialogs.qdoc
@@ -29,7 +29,7 @@
     \example webengine/customdialogs
     \title WebEngine Qt Quick Custom Dialogs Example
     \ingroup webengine-examples
-    \brief Customizes UI elements of Qt WebEngine's dialogs.
+    \brief Customizes UI elements of \QWE's dialogs.
 
     \image customdialogs.png
 
diff --git a/examples/webengine/minimal/doc/src/minimal.qdoc b/examples/webengine/minimal/doc/src/minimal.qdoc
index 8d12afc7c1494ca771eea7c0b154bf29a475dc36..4fc62bddbf5ec9080381dcfc861938f1c78b7974 100644
--- a/examples/webengine/minimal/doc/src/minimal.qdoc
+++ b/examples/webengine/minimal/doc/src/minimal.qdoc
@@ -29,7 +29,7 @@
     \example webengine/minimal
     \title WebEngine Qt Quick Minimal Example
     \ingroup webengine-examples
-    \brief Displays a web page using the Qt Quick integration of Qt WebEngine.
+    \brief Displays a web page using the Qt Quick integration of \QWE.
 
     \image minimal-example.png
 
@@ -52,7 +52,7 @@
 
     In the \c main function we first set the
     \l{QCoreApplication::organizationName} property. This affects the locations
-    where Qt WebEngine stores persistent and cached data (see also
+    where \QWE stores persistent and cached data (see also
     \l{WebEngineProfile::cachePath} and
     \l{WebEngineProfile::persistentStoragePath}).
 
diff --git a/examples/webenginewidgets/cookiebrowser/doc/src/cookiebrowser.qdoc b/examples/webenginewidgets/cookiebrowser/doc/src/cookiebrowser.qdoc
index a1b4eeb18f6e2bd3cee2600a427d9d802de2b063..316e11a9bb550272d20b08afca85c7efe25d1cb2 100644
--- a/examples/webenginewidgets/cookiebrowser/doc/src/cookiebrowser.qdoc
+++ b/examples/webenginewidgets/cookiebrowser/doc/src/cookiebrowser.qdoc
@@ -29,7 +29,7 @@
     \example webenginewidgets/cookiebrowser
     \title WebEngine Cookie Browser Example
     \ingroup webengine-widgetexamples
-    \brief A cookie browser based on Qt WebEngine Widgets.
+    \brief A cookie browser based on \QWE Widgets.
 
     \image cookiebrowser.png
 
diff --git a/examples/webenginewidgets/html2pdf/doc/src/html2pdf.qdoc b/examples/webenginewidgets/html2pdf/doc/src/html2pdf.qdoc
index eea7f7c09e3e1fecdc5bfa219c7a268bd8344c7c..37fe3eb507de962c76f851e3b1554ba3a84809a5 100644
--- a/examples/webenginewidgets/html2pdf/doc/src/html2pdf.qdoc
+++ b/examples/webenginewidgets/html2pdf/doc/src/html2pdf.qdoc
@@ -29,11 +29,11 @@
     \example webenginewidgets/html2pdf
     \title WebEngine Widgets Html2Pdf Example
     \ingroup webengine-widgetexamples
-    \brief Converts web pages to PDF documents using Qt WebEngine.
+    \brief Converts web pages to PDF documents using \QWE.
 
     \image html2pdf-example.png
 
-    \e {Html2Pdf} demonstrates how to use Qt WebEngine to implement a
+    \e {Html2Pdf} demonstrates how to use \QWE to implement a
     command-line application for converting web pages into PDF documents.
 
     \include examples-run.qdocinc
@@ -90,7 +90,7 @@
     \skipto int main
     \printuntil /^\}/
 
-    Note that to use Qt WebEngine Widgets we need to create a \l QApplication
+    Note that to use \QWE Widgets we need to create a \l QApplication
     and not a \l QCoreApplication, even though this is a command line
     application.
 */
diff --git a/examples/webenginewidgets/maps/doc/src/maps.qdoc b/examples/webenginewidgets/maps/doc/src/maps.qdoc
index 5e4a5cd834167600f72a2cdef0b722c343f361b2..489a5a7809b66b379e71b7eac99d50abec106c29 100644
--- a/examples/webenginewidgets/maps/doc/src/maps.qdoc
+++ b/examples/webenginewidgets/maps/doc/src/maps.qdoc
@@ -38,7 +38,7 @@
 
     The \l {https://www.w3.org/TR/geolocation-API/}{Geolocation API} is a
     JavaScript API that web applications can use to determine the user's
-    physical location to show on a map, for example. As Qt WebEngine relies on
+    physical location to show on a map, for example. As \QWE relies on
     \l {Qt Location} to power this API a viable location backend is needed for
     the target platform.
 
diff --git a/examples/webenginewidgets/minimal/doc/src/minimal.qdoc b/examples/webenginewidgets/minimal/doc/src/minimal.qdoc
index d0b25c4b8058f5273055db123a193bd3b42db522..b04390d2367a3e4d84c8923372773e3f3e612760 100644
--- a/examples/webenginewidgets/minimal/doc/src/minimal.qdoc
+++ b/examples/webenginewidgets/minimal/doc/src/minimal.qdoc
@@ -29,7 +29,7 @@
     \example webenginewidgets/minimal
     \title WebEngine Widgets Minimal Example
     \ingroup webengine-widgetexamples
-    \brief Displays a web page using Qt WebEngine Widgets.
+    \brief Displays a web page using \QWE Widgets.
 
     \image minimal-example.png
 
@@ -53,7 +53,7 @@
 
     In the \c main function we first set the
     \l{QCoreApplication::organizationName} property. This affects the locations
-    where Qt WebEngine stores persistent and cached data (see also
+    where \QWE stores persistent and cached data (see also
     \l{QWebEngineProfile::cachePath} and
     \l{QWebEngineProfile::persistentStoragePath}).
 
diff --git a/examples/webenginewidgets/simplebrowser/doc/src/simplebrowser.qdoc b/examples/webenginewidgets/simplebrowser/doc/src/simplebrowser.qdoc
index b0c42623259e273818686181bac0ced3dfaead34..b5ad1362605c8e6aa392d8e8671593479a6de8f3 100644
--- a/examples/webenginewidgets/simplebrowser/doc/src/simplebrowser.qdoc
+++ b/examples/webenginewidgets/simplebrowser/doc/src/simplebrowser.qdoc
@@ -29,7 +29,7 @@
     \example webenginewidgets/simplebrowser
     \title WebEngine Widgets Simple Browser Example
     \ingroup webengine-widgetexamples
-    \brief A simple browser based on Qt WebEngine Widgets.
+    \brief A simple browser based on \QWE Widgets.
 
     \image simplebrowser.png
 
@@ -267,7 +267,7 @@
     Alternatively we could implement private browsing on the tab-level, with
     some tabs in a window in normal mode, others in private mode.
 
-    Implementing private browsing is quite easy using Qt WebEngine. All one has
+    Implementing private browsing is quite easy using \QWE. All one has
     to do is to create a new \l{QWebEngineProfile} and use it in the
     \l{QWebEnginePage} instead of the default profile. In the example this new
     profile is created and owned by the \c Browser object:
diff --git a/examples/webenginewidgets/spellchecker/doc/src/spellchecker.qdoc b/examples/webenginewidgets/spellchecker/doc/src/spellchecker.qdoc
index ff7b43a1b2cc383a642aa5f60a6b334aecfbc91a..ecdb1c818cb4492095fe6261bf2056db5c522a6b 100644
--- a/examples/webenginewidgets/spellchecker/doc/src/spellchecker.qdoc
+++ b/examples/webenginewidgets/spellchecker/doc/src/spellchecker.qdoc
@@ -41,7 +41,7 @@
     \section1 Dictionaries
 
     To be able to check the spelling, we need to provide the spellchecker with
-    dictionaries. The Qt WebEngine spellchecker supports dictionaries provided by the
+    dictionaries. The \QWE spellchecker supports dictionaries provided by the
     \l {Hunspell project} on all platforms and native dictionaries provided by macOS.
     In this example, we want to support the English and German languages.
 
@@ -102,7 +102,7 @@
     the actual language display name. We will use that mapping to display names
     of dictionaries in the context menu. Spellchecking is disabled by default.
     Therefore we also enable spellchecker and set the \e English dictionary.
-    When Qt WebEngine's spellcheck service initializes, it will try to load the
+    When \QWE's spellcheck service initializes, it will try to load the
     \c bdict dictionaries and to check them for consistency.
     Any errors are logged by using the qWarning() function.
 
diff --git a/examples/webenginewidgets/videoplayer/doc/src/videoplayer.qdoc b/examples/webenginewidgets/videoplayer/doc/src/videoplayer.qdoc
index 9f6add6ae19ba84a5baf746be698a174928a3cd1..5c455345b7d3136843e1df7b081bd43324df1486 100644
--- a/examples/webenginewidgets/videoplayer/doc/src/videoplayer.qdoc
+++ b/examples/webenginewidgets/videoplayer/doc/src/videoplayer.qdoc
@@ -40,8 +40,8 @@
     cross-browser Javascript API that enables a web page to request that one of
     its HTML elements be made to occupy the user's entire screen. It is
     commonly used for full screen video playback via the \c <video> element, but
-    can in principle be used to display any HTML content in full screen mode. Qt
-    WebEngine supports this API, however it is disabled by default. This example
+    can in principle be used to display any HTML content in full screen mode.
+    \QWE supports this API, however it is disabled by default. This example
     shows the steps needed to switch it on, including:
 
     \list
@@ -94,7 +94,7 @@
     \skipto MainWindow::MainWindow
     \printuntil setCentralWidget
 
-    We then configure Qt WebEngine to advertise support for the Fullscreen API:
+    We then configure \QWE to advertise support for the Fullscreen API:
 
     \printline QWebEngineSettings
 
diff --git a/examples/webenginewidgets/webui/doc/src/webui.qdoc b/examples/webenginewidgets/webui/doc/src/webui.qdoc
index 47d9fbad16965a9457ba39773e6cd12d8196f8af..949b358a70fe4a8a7cfb5b30d82a7077ec886177 100644
--- a/examples/webenginewidgets/webui/doc/src/webui.qdoc
+++ b/examples/webenginewidgets/webui/doc/src/webui.qdoc
@@ -35,8 +35,8 @@
 
     \e {WebUI} demonstrates how to implement a custom scheme in a secure way.
 
-    Aside from the built-in URL schemes, such as \c {http} and \c {qrc}, Qt
-    WebEngine may be extended with \e {custom schemes} by creating \e {custom
+    Aside from the built-in URL schemes, such as \c {http} and \c {qrc},
+    \QWE may be extended with \e {custom schemes} by creating \e {custom
     scheme handlers}. This example shows:
 
     \list
@@ -111,7 +111,7 @@
     made already at the top of the \c {main} function. This is so because custom
     schemes need to be registered as early as possible so that that they can be
     passed to all subprocesses. Specifically, custom schemes need to be registered
-    before any other Qt WebEngine classes are instantiated by the application.
+    before any other \QWE classes are instantiated by the application.
 
     \section1 Handling Requests
 
diff --git a/src/core/api/qwebengineurlrequestinfo.cpp b/src/core/api/qwebengineurlrequestinfo.cpp
index ea9081fc152497d6add56bfb5addeaa126862ece..2b8a69c9a253c2f17c6ed205f796a33ec17e2395 100644
--- a/src/core/api/qwebengineurlrequestinfo.cpp
+++ b/src/core/api/qwebengineurlrequestinfo.cpp
@@ -82,7 +82,7 @@ ASSERT_ENUMS_MATCH(QtWebEngineCore::WebContentsAdapterClient::OtherNavigation, Q
     The QWebEngineUrlRequestInfo is useful for setting extra header fields for requests
     or for redirecting certain requests without payload data to another URL.
     This class cannot be instantiated or copied by the user, instead it will
-    be created by Qt WebEngine and sent through the virtual function
+    be created by \QWE and sent through the virtual function
     QWebEngineUrlRequestInterceptor::interceptRequest() if an interceptor has been set.
 */
 
diff --git a/src/core/api/qwebengineurlscheme.cpp b/src/core/api/qwebengineurlscheme.cpp
index 9f7288f2d57a61d83e53e41e582d018b900f707c..9b04f46c584fe2ca30affdf0fc0a6169ad14c24b 100644
--- a/src/core/api/qwebengineurlscheme.cpp
+++ b/src/core/api/qwebengineurlscheme.cpp
@@ -88,7 +88,7 @@ public:
   URLs.
 
   Custom URL schemes must be configured early at application startup, before
-  creating any Qt WebEngine classes. In general this means the schemes need to be configured before
+  creating any \QWE classes. In general this means the schemes need to be configured before
   a QGuiApplication or QApplication instance is created.
 
   Every registered scheme configuration applies globally to all profiles.
diff --git a/src/core/doc/src/qtwebenginecore-index.qdoc b/src/core/doc/src/qtwebenginecore-index.qdoc
index 4d540e277c4c369df633090a4d5a50e52c129a13..692e33d1dac433cd6dade0065b9d76d8b6ceea0b 100644
--- a/src/core/doc/src/qtwebenginecore-index.qdoc
+++ b/src/core/doc/src/qtwebenginecore-index.qdoc
@@ -29,9 +29,9 @@
     \page qtwebenginecore-index.html
     \title Qt WebEngine Core
 
-    \brief Provides common API shared by Qt WebEngine and Qt WebEngine Widgets.
+    \brief Provides common API shared by \QWE and \QWE Widgets.
 
-    Qt WebEngine Core provides API shared by \l {Qt WebEngine} and \l {Qt WebEngine Widgets}.
+    \QWE Core provides API shared by \l {Qt WebEngine} and \l {Qt WebEngine Widgets}.
 
     \section1 Getting Started
 
@@ -61,7 +61,7 @@
     This is a snapshot of the integration of Chromium into Qt.
 
     Qt Commercial Edition licensees that wish to distribute applications that
-    use the Qt WebEngine module need to be aware of their obligations under the
+    use the \QWE module need to be aware of their obligations under the
     GNU Library General Public License (LGPLv2).
 
     Developers using the Open Source Edition can choose to redistribute
diff --git a/src/core/doc/src/qtwebenginecore-module.qdoc b/src/core/doc/src/qtwebenginecore-module.qdoc
index 65e0766de5bed07de99c6101b2f4f6ed983450ab..c976d024cf15f295edaab7982eb13d15594e5f72 100644
--- a/src/core/doc/src/qtwebenginecore-module.qdoc
+++ b/src/core/doc/src/qtwebenginecore-module.qdoc
@@ -39,7 +39,7 @@
 
     \snippet qtwebenginecore_build_snippet.qdoc 1
 
-    If you use qmake to build your projects, Qt WebEngine Core is usually
+    If you use qmake to build your projects, \QWE Core is usually
     indirectly included through the \l{Qt WebEngine QML Types}{Qt WebEngine} or
     \l{Qt WebEngine Widgets C++ Classes}{Qt WebEngine Widgets} modules.
 
diff --git a/src/webengine/api/qquickwebenginedownloaditem.cpp b/src/webengine/api/qquickwebenginedownloaditem.cpp
index 981d116330332032f20e071e56369a0d18b156bc..cdb95fa53e6d691b11a91e1779627cfb89ecf390 100644
--- a/src/webengine/api/qquickwebenginedownloaditem.cpp
+++ b/src/webengine/api/qquickwebenginedownloaditem.cpp
@@ -135,7 +135,7 @@ QQuickWebEngineDownloadItemPrivate::~QQuickWebEngineDownloadItemPrivate()
     \l{WebEngineProfile::downloadRequested}{downloadRequested} signal together
     with a newly created WebEngineDownloadItem. The application can then examine
     this item and decide whether to accept it or not. A signal handler must
-    explicitly call accept() on the item for Qt WebEngine to actually start
+    explicitly call accept() on the item for \QWE to actually start
     downloading and writing data to disk. If no signal handler calls accept(),
     then the download request will be automatically rejected and nothing will be
     written to disk.
@@ -154,7 +154,7 @@ QQuickWebEngineDownloadItemPrivate::~QQuickWebEngineDownloadItemPrivate()
     \section2 Web Page Downloads
 
     In addition to normal file downloads, which consist simply of retrieving
-    some raw bytes from the network and writing them to disk, Qt WebEngine also
+    some raw bytes from the network and writing them to disk, \QWE also
     supports saving complete web pages, which involves parsing the page's HTML,
     downloading any dependent resources, and potentially packaging everything
     into a special file format (\l savePageFormat). To check if a download is
diff --git a/src/webengine/api/qquickwebengineloadrequest.cpp b/src/webengine/api/qquickwebengineloadrequest.cpp
index b3422c516374fa1a06438e3d7c5232a00ddace0c..5ad99ea2e858138266e83fa73072c4a17ec2da2e 100644
--- a/src/webengine/api/qquickwebengineloadrequest.cpp
+++ b/src/webengine/api/qquickwebengineloadrequest.cpp
@@ -127,7 +127,7 @@ QString QQuickWebEngineLoadRequest::errorString() const
     \value  WebEngineView.NoErrorDomain
             Error type is not known.
     \value  WebEngineView.InternalErrorDomain
-            Content cannot be interpreted by Qt WebEngine.
+            Content cannot be interpreted by \QWE.
     \value  WebEngineView.ConnectionErrorDomain
             Error results from a faulty network connection.
     \value  WebEngineView.CertificateErrorDomain
diff --git a/src/webengine/api/qtwebengineglobal.cpp b/src/webengine/api/qtwebengineglobal.cpp
index d181f44aaa59bef05a354a6e1220e70a9504c32f..a11618dba8e5e82ade5abb9824985837591cd255 100644
--- a/src/webengine/api/qtwebengineglobal.cpp
+++ b/src/webengine/api/qtwebengineglobal.cpp
@@ -54,9 +54,9 @@ namespace QtWebEngine {
     \ingroup qtwebengine-namespaces
     \keyword QtWebEngine Namespace
 
-    \brief Helper functions for the Qt WebEngine (Qt Quick) module.
+    \brief Helper functions for the \QWE (Qt Quick) module.
 
-    The \l[CPP]{QtWebEngine} namespace is part of the Qt WebEngine module.
+    The \l[CPP]{QtWebEngine} namespace is part of the \QWE module.
 */
 
 /*!
diff --git a/src/webengine/doc/qtwebengine.qdocconf b/src/webengine/doc/qtwebengine.qdocconf
index b1e3a2ded48ae2e8e217e8c8d0ef753ed9ea05ed..50f2e2cebf2a8a6b62a170a5253cce7601daaf71 100644
--- a/src/webengine/doc/qtwebengine.qdocconf
+++ b/src/webengine/doc/qtwebengine.qdocconf
@@ -81,4 +81,7 @@ navigation.landingpage = "Qt WebEngine"
 navigation.cppclassespage = "Qt WebEngine C++ Classes and Namespaces"
 navigation.qmltypespage = "Qt WebEngine QML Types"
 
+# \QWE macro expands to 'Qt WebEngine' without auto-linking anywhere.
+macro.QWE    = "Qt \\WebEngine"
+
 Cpp.ignoretokens += Q_WEBENGINE_EXPORT QWEBENGINEWIDGETS_EXPORT
diff --git a/src/webengine/doc/src/external-resources.qdoc b/src/webengine/doc/src/external-resources.qdoc
index 7ff6eea6b224b77df0bf62ca7a4f134fdea21912..ba9823047bd89823bbf2db2218d459f8d90da7b8 100644
--- a/src/webengine/doc/src/external-resources.qdoc
+++ b/src/webengine/doc/src/external-resources.qdoc
@@ -95,18 +95,6 @@
     \title Hunspell Project
 */
 
-/*
-    This prevents autolinking of each occurrence of 'WebEngine'
-    To link to the WebEngine QML type, use explicit linking:
-        \l [QML] WebEngine
-        \sa {QtWebEngine::}{WebEngine}
-*/
-/*!
-    \externalpage nolink
-    \title WebEngine
-    \internal
-*/
-
 /*!
     \externalpage https://www.w3.org/Protocols/rfc2616/rfc2616-sec19.html#sec19.5.1
     \title RFC 2616 section 19.5.1
diff --git a/src/webengine/doc/src/qtwebengine-debugging.qdoc b/src/webengine/doc/src/qtwebengine-debugging.qdoc
index b8b004095ef467e1cea5dadda40dc7af45e5449b..088db5f871291bf7fd8e4c4dae3e582aec4e874a 100644
--- a/src/webengine/doc/src/qtwebengine-debugging.qdoc
+++ b/src/webengine/doc/src/qtwebengine-debugging.qdoc
@@ -31,7 +31,7 @@
 
     \section1 Console Logging
 
-    JavaScript executed inside Qt WebEngine can use the
+    JavaScript executed inside \QWE can use the
     \l{Chrome console API} to log information to a console. The logging messages
     are forwarded to Qt's logging facilities inside a \c js
     \l{QLoggingCategory}{logging category}. However, only warning and fatal
@@ -40,19 +40,19 @@
     by reimplementing \l{QWebEnginePage::javaScriptConsoleMessage()}, or
     connecting to \l{WebEngineView::javaScriptConsoleMessage()}.
 
-    All messages can also be accessed through the Qt WebEngine developer
+    All messages can also be accessed through the \QWE developer
     tools.
 
     \section1 Qt WebEngine Developer Tools
 
-    The Qt WebEngine module provides web developer tools that make it easy
+    The \QWE module provides web developer tools that make it easy
     to inspect and debug layout and performance issues of any web content.
 
     The developer tools are accessed as a local web page using a Chromium or
-    Qt WebEngine based browser, such as the Chrome browser.
+    \QWE based browser, such as the Chrome browser.
 
-    To activate the developer tools, start an application that uses Qt
-    WebEngine with the command-line arguments:
+    To activate the developer tools, start an application that uses \QWE
+    with the command-line arguments:
 
     \badcode
     --remote-debugging-port=<port_number>
diff --git a/src/webengine/doc/src/qtwebengine-deploying.qdoc b/src/webengine/doc/src/qtwebengine-deploying.qdoc
index c9f0f35808b927d85f0080c4575f1efc73bdbfdc..7b9f3fd4a5e2df0edd203429fe4c3ccd43087a22 100644
--- a/src/webengine/doc/src/qtwebengine-deploying.qdoc
+++ b/src/webengine/doc/src/qtwebengine-deploying.qdoc
@@ -34,7 +34,7 @@
     \l{Deploying Applications on macOS}{macdeployqt} automate the steps to
     generate a stand-alone application package.
 
-    When manually deploying applications that depend on Qt WebEngine, all the
+    When manually deploying applications that depend on \QWE, all the
     files that are required to run the application have to be included:
     libraries, QML imports, plugins, and translations.
 
@@ -42,27 +42,27 @@
 
     \section1 Target Platforms
 
-    Qt WebEngine does try to support all \l{Supported Platforms} of Qt. However,
+    \QWE does try to support all \l{Supported Platforms} of Qt. However,
     due to different requirements of Chromium this is not always possible. Known
     limitations are:
 
     \list
-        \li Qt WebEngine currently supports only Windows, Linux, and \macos.
+        \li \QWE currently supports only Windows, Linux, and \macos.
 
-        \li On Windows, Qt WebEngine only supports Windows Vista or newer as
+        \li On Windows, \QWE only supports Windows Vista or newer as
             target platform. Due to use of newer API in Chromium, Windows XP is
             not supported. WinRT is not supported, either.
     \endlist
 
     \section1 Deploying Applications Manually
 
-    When  manually deploying applications that depend on Qt WebEngine, the
+    When  manually deploying applications that depend on \QWE, the
     following files might have to be deployed:
 
     \list
         \li Libraries
         \li QML imports
-        \li Qt WebEngine process
+        \li \QWE process
         \li Resources
         \li Translations
         \li Audio and video codecs
@@ -71,7 +71,7 @@
     \section2 Deploying Libraries
 
     The following libraries must be deployed with applications that depend on
-    Qt WebEngine:
+    \QWE:
 
     \list
         \li QtWebEngineCore library
@@ -84,10 +84,10 @@
     If Qt Quick integration is used in the application, the QtWebEngine import
     directory needs to be deployed.
 
-    \section2 Deploying Qt WebEngine Processes
+    \section2 Deploying \QWE Processes
 
-    Qt WebEngine takes advantage of the multi-process model that the Chromium
-    project offers. The multi-process model requires that the Qt WebEngine
+    \QWE takes advantage of the multi-process model that the Chromium
+    project offers. The multi-process model requires that the \QWE
     Process executable be deployed alongside your application.
 
     The WebEngine process is executed for each QWebEngineView or WebEngineView
@@ -96,18 +96,18 @@
     running. This is a common approach used by most modern web engines to
     provide a stable browsing experience.
 
-    At runtime, Qt WebEngine looks for the \c QtWebEngineProcess executable in
+    At runtime, \QWE looks for the \c QtWebEngineProcess executable in
     the directory that
     QLibraryInfo::location(QLibraryInfo::LibraryExecutablesPath) returns.
     For Qt installations, this is \c QTDIR/libexec (Linux) or \c QTDIR\bin
     (Windows). The path can be changed by defining a \c qt.conf file, for
     example. Alternatively, an executable path can be set as a value of the
-    \c QTWEBENGINEPROCESS_PATH environment variable. On \macos, Qt WebEngine
+    \c QTWEBENGINEPROCESS_PATH environment variable. On \macos, \QWE
     looks for the executable in \c .app/Helpers/QtWebEngineProcess.
 
     \section2 Deploying Resources
 
-    Qt WebEngine requires the following resource files:
+    \QWE requires the following resource files:
 
     \list
         \li \c qtwebengine_resources.pak contains the resources needed by
@@ -120,7 +120,7 @@
             DPI displays.
         \li \c icudtl.dat provides support for International Components for
             Unicode (ICU). It is the Chromium version of ICU, which is not
-            needed if Qt WebEngine was configured to use the system ICU.
+            needed if \QWE was configured to use the system ICU.
     \endlist
 
     Resources are searched from the following locations:
diff --git a/src/webengine/doc/src/qtwebengine-examples.qdoc b/src/webengine/doc/src/qtwebengine-examples.qdoc
index 24604e3dd1767a202ee2884266acbf8bfd930c18..d31895078caf3fb232e6d57c4433a6f51bd6bd9a 100644
--- a/src/webengine/doc/src/qtwebengine-examples.qdoc
+++ b/src/webengine/doc/src/qtwebengine-examples.qdoc
@@ -28,7 +28,7 @@
 /*!
     \group webengine-examples
     \title Qt WebEngine Examples
-    \brief Examples demonstrating the Qt WebEngine usage.
+    \brief Examples demonstrating the \QWE usage.
     \ingroup all-examples
 
     These examples and demonstrations show a range of different uses for \l{Qt WebEngine},
diff --git a/src/webengine/doc/src/qtwebengine-features.qdoc b/src/webengine/doc/src/qtwebengine-features.qdoc
index 1dce17e0864eb6dd8785a4024b92b9d06b5d22ba..6522fb6f71b1db9ddbc2c583f1563b98c6abee24 100644
--- a/src/webengine/doc/src/qtwebengine-features.qdoc
+++ b/src/webengine/doc/src/qtwebengine-features.qdoc
@@ -29,9 +29,9 @@
     \page qtwebengine-features.html
     \title Qt WebEngine Features
 
-    \brief Summarizes Qt WebEngine features.
+    \brief Summarizes \QWE features.
 
-    Qt WebEngine supports the following features:
+    \QWE supports the following features:
 
     \list
         \li \l{Audio and Video Codecs}
@@ -54,7 +54,7 @@
 
     \section1 Audio and Video Codecs
 
-    Qt WebEngine supports the MPEG-4 Part 14 (MP4) file format only if the
+    \QWE supports the MPEG-4 Part 14 (MP4) file format only if the
     required proprietary audio and video codecs, such as H.264 and MPEG layer-3
     (MP3), have been enabled. Proprietary codecs can be enabled by passing the
     following option to the \c configure tool when configuring Qt:
@@ -72,8 +72,8 @@
 
     For more information, see \l{Qt Configure Options}.
 
-    When using qmake to build just the Qt WebEngine module, the following
-    command can be used (in this example, the Qt WebEngine source code is
+    When using qmake to build just the \QWE module, the following
+    command can be used (in this example, the \QWE source code is
     located in \c {C:\qt\qtwebengine}):
 
     \code
@@ -94,7 +94,7 @@
     The Chromium DevTools provide the ability to inspect and debug layout and
     performance issues of any web content.
 
-    This feature can be tested by launching a Qt WebEngine application with the
+    This feature can be tested by launching a \QWE application with the
     command line option \c {--remote-debugging-port=[your-port]} or by setting
     the environment variable \c QTWEBENGINE_REMOTE_DEBUGGING, and then using a
     Chromium based browser (such as \l{WebEngine Widgets Simple Browser Example}
@@ -115,12 +115,12 @@
     \section1 Client Certificates
 
     Some web servers, in particular many intranet sites, require the client to
-    authenticate itself with a certificate, called a \e {client certificate}. Qt WebEngine
+    authenticate itself with a certificate, called a \e {client certificate}. \QWE
     will read the client certificates installed in the system settings in macOS and
     Windows, and on Linux those installed into the NSS database. Certificates can
     be installed into the NSS database using the \c pk12util tool.
 
-    By default, QtWebEngine will not offer any client certificates to servers, as doing
+    By default, \QWE will not offer any client certificates to servers, as doing
     so uniquely identifies the user and might violate privacy expectations.
 
     To activate support for client certificates, an application needs to listen to
@@ -131,7 +131,7 @@
 
     \section1 Custom Schemes
 
-    Qt WebEngine makes it possible for the application to define its own custom
+    \QWE makes it possible for the application to define its own custom
     URL schemes with specialized security policies and transport mechanisms.
 
     Custom schemes can be used to implement alternative network protocols with
@@ -144,7 +144,7 @@
 
     \section1 Drag and Drop
 
-    Qt WebEngine supports HTML5 drag and drop.
+    \QWE supports HTML5 drag and drop.
 
     This feature can be tested by opening an HTML5 drag and drop demo, such as
     \l{HTML5 Demos - Drag and Drop}, \l{HTML5 Demos - Simple Drag and Drop}, or
@@ -159,7 +159,7 @@
 
     \section1 Fullscreen
 
-    Qt WebEngine supports viewing web content in fullscreen mode. For more
+    \QWE supports viewing web content in fullscreen mode. For more
     information, see \l{WebEngineSettings::fullscreenSupportEnabled}
     {WebEngineSettings.fullscreenSupportEnabled},
     \l{WebEngineView::fullScreenRequested}{WebEngineView.fullScreenRequested},
@@ -175,7 +175,7 @@
 
     \section1 HTML5 DRM
 
-    Qt WebEngine supports viewing DRM protected videos if the \l{Widevine DRM}
+    \QWE supports viewing DRM protected videos if the \l{Widevine DRM}
     plugin has been installed.
 
     The video format most commonly used by DRM services, H.264, requires
@@ -190,12 +190,12 @@
 
     \section1 HTML5 Geolocation
 
-    Qt WebEngine supports JavaScript Geolocation API with \l {Qt Location} as a
+    \QWE supports JavaScript Geolocation API with \l {Qt Location} as a
     backend. The application has to explicitly allow the feature by using
     QWebEnginePage::Geolocation or \l{WebEngineView::Feature}
     {WebEngineView.Feature}.
 
-    If Qt Location has been built before Qt WebEngine then this feature can be
+    If Qt Location has been built before \QWE then this feature can be
     tested by using \l{WebEngine Widgets Maps Example}{Maps} and allowing it to
     find the current position of the user. Note that on Windows an external GPS
     receiver must be connected to the application. For more information, see
@@ -205,7 +205,7 @@
 
     \section1 HTTP/2 Protocol
 
-    Qt WebEngine supports the Chromium implementation of the \l{HTTP/2}
+    \QWE supports the Chromium implementation of the \l{HTTP/2}
     protocol.
 
     This feature can be tested by opening an HTTP/2 demo, such as the
@@ -224,7 +224,7 @@
         \li Displaying form validation messages
     \endlist
 
-    Qt WebEngine provides standard dialogs for these functions. In widget-based
+    \QWE provides standard dialogs for these functions. In widget-based
     applications, the standard dialogs are based on QDialog, whereas in Qt Quick
     applications, they can be based either on Qt Quick Controls 1 or Qt Quick
     Controls 2 (since Qt 5.8). The latter are used only on \c eglfs platforms.
@@ -233,7 +233,7 @@
     Controls 2, set the \c QTWEBENGINE_DIALOG_SET environment variable to either
     \c{QtQuickControls1} or \c{QtQuickControls2}.
 
-    Qt WebEngine Widgets dialogs can be customized by reimplementing the
+    \QWE Widgets dialogs can be customized by reimplementing the
     QWebEnginePage::chooseFiles(), QWebEnginePage::javaScriptAlert(),
     QWebEnginePage::javaScriptConfirm(), and QWebEnginePage::javaScriptPrompt()
     functions.
@@ -248,7 +248,7 @@
 
     \section1 Pepper Plugin API
 
-    Qt WebEngine supports loading Pepper Plugin API (PPAPI) plugins if
+    \QWE supports loading Pepper Plugin API (PPAPI) plugins if
     WebEngineSettings::pluginsEnabled or QWebEngineSettings::PluginsEnabled
     is set.
 
@@ -320,7 +320,7 @@
 
     \section1 Print to PDF
 
-    Qt WebEngine supports printing a web page to a PDF file. For more
+    \QWE supports printing a web page to a PDF file. For more
     information, see QWebEnginePage::printToPdf() and
     \l{WebEngineView::printToPdf}{WebEngineView.printToPdf}.
 
@@ -331,7 +331,7 @@
 
     \section1 Process Models
 
-    Qt WebEngine uses multiple OS processes to isolate web sites from each other
+    \QWE uses multiple OS processes to isolate web sites from each other
     and from the client application, improving security and robustness. The
     following process models, or ways to divide web sites between OS processes,
     are supported:
@@ -354,7 +354,7 @@
     and \c{https://de.wikipedia.org/} would belong to the same site.
 
     A site instance is a collection of web pages belonging to the same site.
-    When the application explicitly loads a URL into Qt WebEngine (via \l
+    When the application explicitly loads a URL into \QWE (via \l
     QWebEnginePage::setUrl, for example), a new site instance is created for the
     page. However, when the user clicks same-site links on the page, the
     existing site instance is merely extended with more pages.
@@ -387,7 +387,7 @@
 
     \section1 Spellchecker
 
-    Qt WebEngine supports integrating spellchecking support into HTML forms to
+    \QWE supports integrating spellchecking support into HTML forms to
     enable users to submit spellchecked messages. When the user clicks on
     an underlined misspelled word, the default context menu displays up to four
     suggestions. Selecting one will replace the misspelled word.
@@ -407,7 +407,7 @@
 
     These two files can be converted into the \c bdic format by using the
     \c qwebengine_convert_dict tool that is shipped together with Qt.
-    When the Qt WebEngine spellchecker initializes, it will try to load the
+    When the \QWE spellchecker initializes, it will try to load the
     \c bdict dictionaries and to check them for consistency.
 
     If \c QTWEBENGINE_DICTIONARIES_PATH is set, the spellchecker uses the
@@ -416,7 +416,7 @@
     executable if it exists. If it does not exist, it will look in \c
     QT_INSTALL_PREFIX/qtwebengine_dictionaries.
 
-    On macOS, depending on how Qt WebEngine is configured at build time, there
+    On macOS, depending on how \QWE is configured at build time, there
     are two possibilities how spellchecking data is found:
 
     \list
@@ -426,7 +426,7 @@
             means the results will depend on the installed OS dictionaries)
     \endlist
 
-    Thus, in the macOS Hunspell case, Qt WebEngine will look in the \e
+    Thus, in the macOS Hunspell case, \QWE will look in the \e
     qtwebengine_dictionaries subdirectory located inside the application bundle
     \c Resources directory, and also in the \c Resources directory located
     inside the Qt framework bundle.
@@ -460,7 +460,7 @@
 
     \section1 Touch
 
-    Qt WebEngine supports touch devices for navigating and interacting with web pages.
+    \QWE supports touch devices for navigating and interacting with web pages.
 
     Applications can prohibit the use of touch events in the following ways:
 
@@ -476,7 +476,7 @@
 
     \section1 View Source
 
-    Qt WebEngine supports viewing the HTML source of a web page.
+    \QWE supports viewing the HTML source of a web page.
 
     This feature can be used from custom menus or assigned to custom events.
     For more information, see WebEngineView::WebAction, and QWebEnginePage::WebAction.
diff --git a/src/webengine/doc/src/qtwebengine-index.qdoc b/src/webengine/doc/src/qtwebengine-index.qdoc
index bd6cc9a326ce2dc94a377db1bb5a8c0f21e140fc..f668cf87bb903fe592f45198b47578292b1b19b8 100644
--- a/src/webengine/doc/src/qtwebengine-index.qdoc
+++ b/src/webengine/doc/src/qtwebengine-index.qdoc
@@ -31,9 +31,9 @@
 
     \brief Provides functionality for rendering regions of dynamic web content.
 
-    \e {Qt WebEngine} provides functionality for rendering regions of dynamic web content.
+    \QWE provides functionality for rendering regions of dynamic web content.
 
-    The functionality in Qt WebEngine is divided into the following modules:
+    The functionality in \QWE is divided into the following modules:
 
     \annotatedlist qtwebengine-modules
 
diff --git a/src/webengine/doc/src/qtwebengine-module.qdoc b/src/webengine/doc/src/qtwebengine-module.qdoc
index 2d4d1b8da9def037ef8fa0777a3997590011af30..5554bd519a86675a65cf4c66a1a872dc49bfdcfe 100644
--- a/src/webengine/doc/src/qtwebengine-module.qdoc
+++ b/src/webengine/doc/src/qtwebengine-module.qdoc
@@ -31,7 +31,7 @@
     \brief Exposes C++ functionality to Qt Quick.
     \ingroup modules
 
-    The Qt WebEngine module exposes C++ functionality to Qt Quick.
+    The \QWE module exposes C++ functionality to Qt Quick.
 
     To include the definitions of the module's classes, use the
     following directive:
diff --git a/src/webengine/doc/src/qtwebengine-overview.qdoc b/src/webengine/doc/src/qtwebengine-overview.qdoc
index d83a65bdb0ee8dfd763cb35b8254e1a62fe3f4ac..8feb38ecac86bd234b83027cac879400a52c3a72 100644
--- a/src/webengine/doc/src/qtwebengine-overview.qdoc
+++ b/src/webengine/doc/src/qtwebengine-overview.qdoc
@@ -29,10 +29,10 @@
     \page qtwebengine-overview.html
     \title Qt WebEngine Overview
 
-    The Qt WebEngine module provides a web browser engine that makes it easy to embed content from
+    The \QWE module provides a web browser engine that makes it easy to embed content from
     the World Wide Web into your Qt application on platforms that do not have a native web engine.
 
-    Qt WebEngine provides C++ classes and QML types for rendering HTML, XHTML, and SVG documents,
+    \QWE provides C++ classes and QML types for rendering HTML, XHTML, and SVG documents,
     styled using Cascading Style Sheets (CSS) and scripted with JavaScript. HTML documents can be
     made fully editable by the user through the use of the \c{contenteditable} attribute on HTML
     elements.
@@ -41,7 +41,7 @@
 
     \image qtwebengine-architecture.png
 
-    The functionality in Qt WebEngine is divided into the following modules:
+    The functionality in \QWE is divided into the following modules:
 
     \list
         \li \l{Qt WebEngine Widgets Module} for creating widget-based web applications
@@ -49,7 +49,7 @@
         \li \l{Qt WebEngine Core Module} for interacting with Chromium
     \endlist
 
-    Page rendering and JavaScript execution are separated from the GUI process into the Qt WebEngine
+    Page rendering and JavaScript execution are separated from the GUI process into the \QWE
     Process. It is a library that must be shipped with the application if the Qt libraries are
     bundled into the application.
 
@@ -57,7 +57,7 @@
 
     \image qtwebenginewidgets-model.png
 
-    A \e {web engine view} is the main widget component of the Qt WebEngine module. It can be used
+    A \e {web engine view} is the main widget component of the \QWE module. It can be used
     in various applications to load web content. Within a view, a \e {web engine page} holds a main
     frame that is responsible for web content, the \e history of navigated links, and \e actions.
     The view and page are quite similar, as they provide a set of common functions.
@@ -66,7 +66,7 @@
     \e cookies. Profiles can be used to isolate pages from each other. A typical use case is a
     dedicated profile for a \e {private browsing} mode, where no information is permanently saved.
 
-    \note The Qt WebEngine Widgets module uses the \l{Qt Quick Scene Graph}{Qt Quick scene graph}
+    \note The \QWE Widgets module uses the \l{Qt Quick Scene Graph}{Qt Quick scene graph}
     to compose the elements of a web page into one view. This means that the UI process
     requires OpenGL ES 2.0 or OpenGL 2.0 for its rendering.
 
@@ -74,27 +74,27 @@
 
     \image qtwebengine-model.png
 
-    The Qt WebEngine QML implementation contains the same elements as the Qt WebEngine Widgets
+    The \QWE QML implementation contains the same elements as the \QWE Widgets
     implementation, except that there is no separately accessible web engine page.
     The supported page functionality is integrated into the web engine view.
 
     \section2 Qt WebEngine Core Module
 
-    The Qt WebEngine core is based on the \l {Chromium Project}. Chromium provides its own network
+    The \QWE core is based on the \l {Chromium Project}. Chromium provides its own network
     and painting engines and is developed tightly together with its dependent modules.
 
-    \note Qt WebEngine is based on Chromium, but does not contain or use any services
+    \note \QWE is based on Chromium, but does not contain or use any services
     or add-ons that might be part of the Chrome browser that is built and delivered by Google.
     You can find more detailed information about the differences between Chromium and Chrome in this
     \l{https://chromium.googlesource.com/chromium/src/+/master/docs/chromium_browser_vs_google_chrome.md}{overview}
     that is part of the documentation in the \l {Chromium Project} upstream source tree.
 
-    This version of Qt WebEngine is based on Chromium version 69.0.3497.128, with
+    This version of \QWE is based on Chromium version 69.0.3497.128, with
     additional security fixes from newer versions.
 
     \section2 Qt WebEngine Process
 
-    The Qt WebEngine Process is a separate executable that is used to render web pages and
+    The \QWE Process is a separate executable that is used to render web pages and
     execute JavaScript. This mitigates security issues and isolates crashes caused by specific
     content.
 
@@ -177,7 +177,7 @@
 
     \section1 Script Injection
 
-    Qt WebEngine does not allow direct access to the document object model (DOM) of a page.
+    \QWE does not allow direct access to the document object model (DOM) of a page.
     However, the DOM can be inspected and adapted by injecting scripts.
 
     The DOM of a page is constructed when the document is ready, typically
@@ -191,7 +191,7 @@
     script to run, the injection point, and the world where the script is run. This enables
     accessing the DOM to manipulate it within a world.
 
-    Since Qt 5.8, Qt WebEngine supports augmenting a script by using the
+    Since Qt 5.8, \QWE supports augmenting a script by using the
     following \l{Metadata Block}{Greasemonkey-like attributes}:
 
     \list
@@ -221,8 +221,8 @@
 
     \section1 Managing Certificates
 
-    Qt WebEngine uses its own network stack, and therefore QSslConfiguration is not used to
-    open SSL connections. Instead, Qt WebEngine uses the root CA certificates from the operating
+    \QWE uses its own network stack, and therefore QSslConfiguration is not used to
+    open SSL connections. Instead, \QWE uses the root CA certificates from the operating
     system to validate the peer's certificate.
 
     The \l{WebEngineCertificateError::error} and \l{QWebEngineCertificateError::Error} enumerations
@@ -232,13 +232,13 @@
 
     \section1 Proxy Support
 
-    Qt WebEngine uses the proxy settings from \l{Qt Network}, and forwards them to Chromium's
-    networking stack. If QNetworkProxy::applicationProxy is set, it will also be used for Qt
-    WebEngine. If QNetworkProxyFactory::usesSystemConfiguration() is enabled, the proxy settings
+    \QWE uses the proxy settings from \l{Qt Network}, and forwards them to Chromium's
+    networking stack. If QNetworkProxy::applicationProxy is set, it will also be used for \QWE.
+    If QNetworkProxyFactory::usesSystemConfiguration() is enabled, the proxy settings
     are automatically retrieved from the system. Settings from an installed QNetworkProxyFactory
     will be ignored, though.
 
-    Not all properties of QNetworkProxy are supported by Qt WebEngine. That is,
+    Not all properties of QNetworkProxy are supported by \QWE. That is,
     QNetworkProxy::type(), QNetworkProxy::hostName() and QNetworkProxy::port() are taken into
     account. All other proxy settings such as QNetworkProxy::rawHeader(), QNetworkProxy::user(), or
     QNetworkProxy::password() are ignored.
@@ -250,7 +250,7 @@
 
     To support High DPI devices, it is recommended that the application attribute
     Qt::AA_EnableHighDpiScaling is set to enable automatic scaling based on the
-    pixel density of the monitor. In Qt WebEngine applications, the scaling
+    pixel density of the monitor. In \QWE applications, the scaling
     affects the default zooming factor and scrollbar size.
 
     For example:
@@ -264,7 +264,7 @@
     }
     \endcode
 
-    Qt WebEngine bundles images for normal and high-dpi resolutions into
+    \QWE bundles images for normal and high-dpi resolutions into
     \e qtwebengine_resources_100p.pak and \e qtwebengine_resources_200p.pak
     files. Depending on the target resolutions, one or both of these files need
     to be deployed.
@@ -273,7 +273,7 @@
 
     \section1 Using WebEngine Core
 
-    Qt WebEngine Core provides an API shared by Qt WebEngine and Qt WebEngine Widgets for handling
+    \QWE Core provides an API shared by \QWE and \QWE Widgets for handling
     URL requests issued for the networking stack of Chromium and for accessing its HTTP cookies.
 
     Implementing the QWebEngineUrlRequestInterceptor interface and installing the interceptor on a
@@ -290,17 +290,17 @@
 
     \section1 Platform Notes
 
-    Qt WebEngine currently supports only Windows, Linux, and \macos. Due to Chromium build
+    \QWE currently supports only Windows, Linux, and \macos. Due to Chromium build
     requirements it also often requires a newer compiler than the rest of Qt. See
     \l{Qt WebEngine Platform Notes} for further details.
 
     \section1 Related Modules
 
-    Qt WebEngine supersedes the \l{http://doc.qt.io/archives/qt-5.3/qtwebkit-index.html}{Qt WebKit}
+    \QWE supersedes the \l{http://doc.qt.io/archives/qt-5.3/qtwebkit-index.html}{Qt WebKit}
     module, which is based on the
     WebKit project, but has not been actively synchronized with the upstream WebKit code since
-    Qt 5.2 and has been deprecated in Qt 5.5. For tips on how to change a Qt WebKit widgets
-    application to use Qt WebEngine widgets, see \l{Porting from Qt WebKit to Qt WebEngine}.
+    Qt 5.2 and has been deprecated in Qt 5.5. For tips on how to change a Qt \WebKit widgets
+    application to use \QWE widgets, see \l{Porting from Qt WebKit to Qt WebEngine}.
 
     The \l{Qt WebView} module allows to use a native web browser on platforms where one is
     available.
diff --git a/src/webengine/doc/src/qtwebengine-platform-notes.qdoc b/src/webengine/doc/src/qtwebengine-platform-notes.qdoc
index 0b2aebfce141ea0b598f13a0f492cda076e1778f..fefb477954ed7a41cc42984ccad6042ff183b075 100644
--- a/src/webengine/doc/src/qtwebengine-platform-notes.qdoc
+++ b/src/webengine/doc/src/qtwebengine-platform-notes.qdoc
@@ -29,9 +29,9 @@
     \page qtwebengine-platform-notes.html
     \title Qt WebEngine Platform Notes
 
-    \brief Contains information about issues that are specific to the Qt WebEngine module.
+    \brief Contains information about issues that are specific to the \QWE module.
 
-    \section1 Building Qt WebEngine from Source
+    \section1 Building \QWE from Source
 
     Static builds are not supported.
 
@@ -53,7 +53,7 @@
         \li \l {macOS}
     \endlist
 
-    The tests for skipping the Qt WebEngine build are located in the
+    The tests for skipping the \QWE build are located in the
     \c qtwebengine repository, in the \c tools\qmake\mkspecs subdirectory.
     They can be found by searching for \c skipBuild.
 
@@ -71,8 +71,8 @@
 
     On Windows, Visual Studio 2017 and Windows 10 SDK are required.
 
-    Qt WebEngine can only be built on 64-bit Windows, with a x64-bit toolchain.
-    For building Qt WebEngine for x86 applications, you need to configure
+    \QWE can only be built on 64-bit Windows, with a x64-bit toolchain.
+    For building \QWE for x86 applications, you need to configure
     and compile Qt with the Visual Studio 2017 x64 to x86 cross-compile
     toolchain. This toolchain can be set up on the command line by running
     \c{vcvarsall.bat amd64_x86}.
@@ -82,7 +82,7 @@
     On Linux, Clang or GCC version 5 or later is required.
     Supported configurations are \c linux-g++ and \c{linux-clang}.
 
-    Qt WebEngine requires \c pkg-config to detect most of its dependencies. The
+    \QWE requires \c pkg-config to detect most of its dependencies. The
     following \c pkg-config files are required:
 
     \list
@@ -115,13 +115,13 @@
         \li \macos 10.12 SDK or later
     \endlist
 
-    \note Qt WebEngine cannot be built for the 32-bit mode of \macos (using the
+    \note \QWE cannot be built for the 32-bit mode of \macos (using the
     \c macx-clang-32 \c mkspec).
 
-    \section1 Using Earlier Qt Versions to Build Qt WebEngine
+    \section1 Using Earlier Qt Versions to Build \QWE
 
-    Building Qt WebEngine with earlier Qt versions (down to the last LTS
-    version) is supported. It means that Qt WebEngine 5.11 can be built with
+    Building \QWE with earlier Qt versions (down to the last LTS
+    version) is supported. It means that \QWE 5.11 can be built with
     Qt 5.9.x, Qt 5.10.x, and Qt 5.11.
 
     To use an earlier Qt version to build Qt Webengine:
@@ -134,7 +134,7 @@
 
     \section1 Mac App Store Compatibility
 
-    Applications using Qt WebEngine are not compatible with the Mac App Store, because:
+    Applications using \QWE are not compatible with the Mac App Store, because:
 
     \list
         \li The Chromium part of the code uses several private API methods, which are prohibited by
@@ -150,7 +150,7 @@
 
     \section1 macOS Airplay Support on MacBooks with Dual GPUs
 
-    To make Qt WebEngine work correctly when streaming to an AppleTV from a MacBook that supports
+    To make \QWE work correctly when streaming to an AppleTV from a MacBook that supports
     GPU switching, it is important to add the \c NSSupportsAutomaticGraphicsSwitching option to the
     application Info.plist file, with the value set to \c YES. Otherwise rendering issues might
     occur when creating new web engine view instances after Airplay is switched on or off.
@@ -167,9 +167,9 @@
 
     \section1 Sandboxing Support
 
-    Qt WebEngine provides out-of-the-box sandboxing support for Chromium render processes on Linux
+    \QWE provides out-of-the-box sandboxing support for Chromium render processes on Linux
     and \macos. Sandboxing is currently not supported on Windows due to a limitation in how
-    the sandbox is set up and how it interacts with the host process provided by the Qt WebEngine
+    the sandbox is set up and how it interacts with the host process provided by the \QWE
     libraries.
 
     On \macos, there are no special requirements for enabling sandbox support.
@@ -184,7 +184,7 @@
 
     \section1 Accessibility and Performance
 
-    Qt WebEngine enables accessibility support for web pages when the following conditions
+    \QWE enables accessibility support for web pages when the following conditions
     are met:
 
     \list
@@ -197,7 +197,7 @@
     Due to some limitations, the Linux QPA plugin almost always reports that accessibility should
     be activated. On big HTML pages, this can cause a significant slowdown in rendering speed.
 
-    Because of that, from Qt 5.9 onwards, Qt WebEngine accessibility support is disabled by default
+    Because of that, from Qt 5.9 onwards, \QWE accessibility support is disabled by default
     on Linux.
     It can be re-enabled by setting the \c QTWEBENGINE_ENABLE_LINUX_ACCESSIBILITY environment
     variable to a non-empty value.
diff --git a/src/webengine/doc/src/qwebengine-licensing.qdoc b/src/webengine/doc/src/qwebengine-licensing.qdoc
index fa5d656d082b3d4d2e29a1d40a50ff5a52a5a719..8795ca44cf2f7ddd9334cb4f2b6d8b3116e869db 100644
--- a/src/webengine/doc/src/qwebengine-licensing.qdoc
+++ b/src/webengine/doc/src/qwebengine-licensing.qdoc
@@ -30,7 +30,7 @@
 \group qtwebengine-licensing
 \title Qt WebEngine Licensing
 
-The Qt specific parts of the Qt WebEngine module are dual-licensed
+The Qt specific parts of the \QWE module are dual-licensed
 under Commercial and GNU Lesser General Public License (LGPLv3).
 In addition, the module contains code licensed under LGPLv2.
 
diff --git a/src/webengine/doc/src/webengineview_lgpl.qdoc b/src/webengine/doc/src/webengineview_lgpl.qdoc
index 0e25e16f3b6d8c623174d4c5728d20d36e7b30fc..23d3049fd5f17e381d49e27d3d3b583144ad06ba 100644
--- a/src/webengine/doc/src/webengineview_lgpl.qdoc
+++ b/src/webengine/doc/src/webengineview_lgpl.qdoc
@@ -213,7 +213,7 @@
 
     An internal URL for accessing the currently displayed web site icon,
     also known as favicon or shortcut icon. The icon is already downloaded
-    and stored by the Qt WebEngine's favicon manager.
+    and stored by the \QWE's favicon manager.
     This read-only URL corresponds to the image used within a mobile browser
     application to represent a bookmarked page on the device's home screen.
 
@@ -230,7 +230,7 @@
     \endqml
 
     Specifying the \c{sourceSize} property of the \c{Image} element informs
-    the Qt WebEngine's favicon provider about the requested size. The
+    the \QWE's favicon provider about the requested size. The
     favicon provider tries to find the best fit among the web page candidate
     icons. If \c{sourceSize} property is not specified, the provider provides
     the icon with the largest resolution.
@@ -629,7 +629,7 @@
 
     \value WebEngineView.NoErrorDomain
     \value WebEngineView.InternalErrorDomain
-            Content fails to be interpreted by Qt WebEngine.
+            Content fails to be interpreted by \QWE.
     \value WebEngineView.ConnectionErrorDomain
             Error results from faulty network connection.
     \value WebEngineView.CertificateErrorDomain
diff --git a/src/webenginewidgets/api/qwebenginedownloaditem.cpp b/src/webenginewidgets/api/qwebenginedownloaditem.cpp
index deb92bfd36be4b06ff8d6d8c9a22c5a078657d56..4575f29294318f8dd5eae252ea730f627332a076 100644
--- a/src/webenginewidgets/api/qwebenginedownloaditem.cpp
+++ b/src/webenginewidgets/api/qwebenginedownloaditem.cpp
@@ -117,7 +117,7 @@ static inline QWebEngineDownloadItem::DownloadInterruptReason toDownloadInterrup
     \l{QWebEngineProfile::downloadRequested}{downloadRequested} signal together
     with a newly created QWebEngineDownloadItem. The application can then
     examine this item and decide whether to accept it or not. A signal handler
-    must explicitly call accept() on the item for Qt WebEngine to actually start
+    must explicitly call accept() on the item for \QWE to actually start
     downloading and writing data to disk. If no signal handler calls accept(),
     then the download request will be automatically rejected and nothing will be
     written to disk.
@@ -147,7 +147,7 @@ static inline QWebEngineDownloadItem::DownloadInterruptReason toDownloadInterrup
     \section2 Web Page Downloads
 
     In addition to normal file downloads, which consist simply of retrieving
-    some raw bytes from the network and writing them to disk, Qt WebEngine also
+    some raw bytes from the network and writing them to disk, \QWE also
     supports saving complete web pages, which involves parsing the page's HTML,
     downloading any dependent resources, and potentially packaging everything
     into a special file format (\l savePageFormat). To check if a download is
diff --git a/src/webenginewidgets/doc/src/qtwebenginewidgets-examples.qdoc b/src/webenginewidgets/doc/src/qtwebenginewidgets-examples.qdoc
index b6c5cb497e3193b4fcea34049b4eb68c051cff97..a9e0e69ead519e85613866da32a27bdf5965dd9b 100644
--- a/src/webenginewidgets/doc/src/qtwebenginewidgets-examples.qdoc
+++ b/src/webenginewidgets/doc/src/qtwebenginewidgets-examples.qdoc
@@ -28,13 +28,13 @@
 /*!
     \group webengine-widgetexamples
     \title Qt WebEngine Widgets Examples
-    \brief Examples demonstrating the Qt WebEngine Widgets usage.
+    \brief Examples demonstrating the \QWE Widgets usage.
     \ingroup all-examples
 
     Qt provides an integrated Web browser component based on Chromium, the popular
     open source browser engine.
 
-    These examples and demonstrations show a range of different uses for Qt WebEngine,
+    These examples and demonstrations show a range of different uses for \QWE,
     from displaying Web pages within a Qt user interface to an implementation of
     a basic function Web browser.
 */
diff --git a/src/webenginewidgets/doc/src/qtwebenginewidgets-index.qdoc b/src/webenginewidgets/doc/src/qtwebenginewidgets-index.qdoc
index abfd17ce359fb1a8c35f5670aeed7566effbdd36..b93bc86f25cc0a1e27857ede267dcdc8d373a08a 100644
--- a/src/webenginewidgets/doc/src/qtwebenginewidgets-index.qdoc
+++ b/src/webenginewidgets/doc/src/qtwebenginewidgets-index.qdoc
@@ -67,7 +67,7 @@
     This is a snapshot of the integration of Chromium into Qt.
 
     Qt Commercial Edition licensees that wish to distribute applications that
-    use the Qt WebEngine module need to be aware of their obligations under the
+    use the \QWE module need to be aware of their obligations under the
     GNU Library General Public License (LGPLv2).
 
     Developers using the Open Source Edition can choose to redistribute
diff --git a/src/webenginewidgets/doc/src/qtwebenginewidgets-module.qdoc b/src/webenginewidgets/doc/src/qtwebenginewidgets-module.qdoc
index 35fed802c27b3916900ad8270707637b54b212c4..6f3eac5adb25c0b7a1b18143135b417f45c8d724 100644
--- a/src/webenginewidgets/doc/src/qtwebenginewidgets-module.qdoc
+++ b/src/webenginewidgets/doc/src/qtwebenginewidgets-module.qdoc
@@ -33,7 +33,7 @@
     \ingroup qtwebengine-modules
     \qtvariable webenginewidgets
 
-    The Qt WebEngineWidgets module provides a web browser engine as well as C++ classes to render
+    The \QWEWidgets module provides a web browser engine as well as C++ classes to render
     and interact with web content.
 
     To include the definitions of the module's classes, use the
diff --git a/src/webenginewidgets/doc/src/qtwebkitportingguide.qdoc b/src/webenginewidgets/doc/src/qtwebkitportingguide.qdoc
index 7bc7ff48d1587173d527bd56350fc19eec6ec47a..e3fdc4ff1067b1f784d6d6fd65f026b98ada0347 100644
--- a/src/webenginewidgets/doc/src/qtwebkitportingguide.qdoc
+++ b/src/webenginewidgets/doc/src/qtwebkitportingguide.qdoc
@@ -28,7 +28,7 @@
 /*!
     \page qtwebenginewidgets-qtwebkitportingguide.html
     \title Porting from Qt WebKit to Qt WebEngine
-    \brief Overview of the differences between the Qt WebKit and Qt WebEngine API.
+    \brief Overview of the differences between the Qt \WebKit and \QWE API.
 
     The following sections contain information about porting an application that uses the
     \l{http://doc.qt.io/archives/qt-5.3/qtwebkit-index.html}{Qt WebKit}
@@ -37,17 +37,17 @@
 
     \section1 Architecture
 
-    Chromium provides its own network and painting engines, which Qt WebEngine uses. This, among
-    other things, allows Qt WebEngine to provide better and more reliable support for the latest
-    HTML5 specification than Qt WebKit. However, Qt WebEngine is thus also heavier than Qt WebKit
+    Chromium provides its own network and painting engines, which \QWE uses. This, among
+    other things, allows \QWE to provide better and more reliable support for the latest
+    HTML5 specification than Qt \WebKit. However, \QWE is thus also heavier than Qt \WebKit
     and does not provide direct access to the network stack and the HTML document through C++ APIs.
 
     \section1 Class Names
 
-    The Qt WebEngine equivalent of Qt WebKit C++ classes are prefixed by
+    The \QWE equivalent of Qt \WebKit C++ classes are prefixed by
     "\e QWebEngine" instead of "\e QWeb".
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         #include <QWebHistory>
         #include <QWebHistoryItem>
@@ -59,7 +59,7 @@
         QWebPage
         QWebView
     \endcode
-    \b {Qt WebEngine}
+    \b {\QWE}
     \code
         #include <QWebEngineHistory>
         #include <QWebEngineHistoryItem>
@@ -77,23 +77,23 @@
 
     \section2 In qmake Project Files
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         QT += webkitwidgets
     \endcode
-    \b {Qt WebEngine}
+    \b {\QWE}
     \code
         QT += webenginewidgets
     \endcode
 
     \section2 Including the Module in Source Files
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         #include <QtWebKit/QtWebKit>
         #include <QtWebKitWidgets/QtWebKitWidgets> // With Qt >= 4.8
     \endcode
-    \b {Qt WebEngine}
+    \b {\QWE}
     \code
         #include <QtWebEngineWidgets/QtWebEngineWidgets>
     \endcode
@@ -104,22 +104,22 @@
     HTML frames can be used to divide web pages into several areas where the content can be
     represented individually.
 
-    In Qt WebKit, QWebFrame represents a frame inside a web page. Each QWebPage object contains at
+    In Qt \WebKit, QWebFrame represents a frame inside a web page. Each QWebPage object contains at
     least one frame, the main frame, obtained using QWebPage::mainFrame(). Additional frames will
     be created for the HTML \c <frame> element, which defines the appearance and contents of a
     single frame, or the \c <iframe> element, which inserts a frame within a block of text.
 
-    In Qt WebEngine, frame handling has been merged into the QWebEnginePage class. All child frames
+    In \QWE, frame handling has been merged into the QWebEnginePage class. All child frames
     are now considered part of the content, and only accessible through JavaScript. Methods of the
     QWebFrame class, such as \c load() are now available directly through the QWebEnginePage itself.
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         QWebPage page;
         connect(page.mainFrame(), SIGNAL(urlChanged(const QUrl&)), SLOT(mySlotName()));
         page.mainFrame()->load(url);
     \endcode
-    \b {Qt WebEngine}
+    \b {\QWE}
     \code
         QWebEnginePage page;
         connect(&page, SIGNAL(urlChanged(const QUrl&)), SLOT(mySlotName()));
@@ -129,12 +129,12 @@
 
     \section1 Some Methods Now Return Their Result Asynchronously
 
-    Because Qt WebEngine uses a multi-process architecture, calls to some methods from applications
+    Because \QWE uses a multi-process architecture, calls to some methods from applications
     will return immediately, while the results should be received asynchronously via a callback
     mechanism. A function pointer, a functor, or a lambda expression must be provided to handle the
     results when they become available.
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         QWebPage *page = new QWebPage;
         QTextEdit *textEdit = new QTextEdit;
@@ -142,7 +142,7 @@
         textEdit->setPlainText(page->toHtml());
         textEdit->setPlainText(page->toPlainText());
     \endcode
-    \b {Qt WebEngine (with a lambda function in C++11)}
+    \b {\QWE (with a lambda function in C++11)}
     \code
         QWebEnginePage *page = new QWebEnginePage;
         QTextEdit *textEdit = new QTextEdit;
@@ -150,7 +150,7 @@
         page->toHtml([textEdit](const QString &result){ textEdit->setPlainText(result); });
         page->toPlainText([textEdit](const QString &result){ textEdit->setPlainText(result); });
     \endcode
-    \b {Qt WebEngine (with a functor template wrapping a member function)}
+    \b {\QWE (with a functor template wrapping a member function)}
     \code
         template<typename Arg, typename R, typename C>
         struct InvokeWrapper {
@@ -174,7 +174,7 @@
         page->toHtml(invoke(textEdit, &QTextEdit::setPlainText));
         page->toPlainText(invoke(textEdit, &QTextEdit::setPlainText));
     \endcode
-    \b {Qt WebEngine (with a regular functor)}
+    \b {\QWE (with a regular functor)}
     \code
         struct SetPlainTextFunctor {
             QTextEdit *textEdit;
@@ -192,29 +192,29 @@
     \endcode
 
 
-    \section1 Qt WebEngine Does Not Interact with QNetworkAccessManager
+    \section1 \QWE Does Not Interact with QNetworkAccessManager
 
     Some classes of Qt Network such as QAuthenticator were reused for their interface
-    but, unlike Qt WebKit, Qt WebEngine has its own HTTP implementation and cannot
+    but, unlike Qt \WebKit, \QWE has its own HTTP implementation and cannot
     go through a QNetworkAccessManager.
 
     The signals and methods of QNetworkAccessManager that are still supported were
     moved to the QWebEnginePage class.
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         QNetworkAccessManager qnam;
         QWebPage page;
         page.setNetworkAccessManager(&qnam);
         connect(&qnam, SIGNAL(authenticationRequired(QNetworkReply*,QAuthenticator*)), this, SLOT(authenticate(QNetworkReply*,QAuthenticator*)));
     \endcode
-    \b {Qt WebEngine}
+    \b {\QWE}
     \code
         QWebEnginePage page;
         connect(&page, SIGNAL(authenticationRequired(QNetworkReply*,QAuthenticator*)), this, SLOT(authenticate(QNetworkReply*,QAuthenticator*)));
     \endcode
 
-    \note In Qt WebEngine, the QAuthenticator must be explicitly set to null to
+    \note In \QWE, the QAuthenticator must be explicitly set to null to
     cancel authentication:
 
     \code
@@ -233,12 +233,12 @@
     It is currently only possible to run JavaScript on the main frame of a page and the
     result is returned asynchronously to the provided functor.
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         QWebPage *page = new QWebPage;
         qDebug() << page->mainFrame()->evaluateJavaScript("'Java' + 'Script'");
     \endcode
-    \b {Qt WebEngine (with lambda expressions in C++11)}
+    \b {\QWE (with lambda expressions in C++11)}
     \code
         QWebEnginePage *page = new QWebEnginePage;
         page->runJavaScript("'Java' + 'Script'", [](const QVariant &result){ qDebug() << result; });
@@ -255,12 +255,12 @@
     the contentEditable attribute in the latest HTML standard. Therefore, QWebEnginePage::runJavaScript
     is all that is needed.
 
-    \b {Qt WebKit}
+    \b {Qt \WebKit}
     \code
         QWebPage page;
         page.setContentEditable(true);
     \endcode
-    \b {Qt WebEngine}
+    \b {\QWE}
     \code
         QWebEnginePage page;
         page.runJavaScript("document.documentElement.contentEditable = true");
@@ -269,35 +269,35 @@
 
     \section1 Unavailable Qt WebKit API
 
-    The Qt WebKit classes and methods in this list will not be available in Qt WebEngine.
+    The Qt \WebKit classes and methods in this list will not be available in \QWE.
 
     \table
     \row
         \li QGraphicsWebView
-        \li Qt WebEngine is designed for being used with hardware acceleration. Because we could not
+        \li \QWE is designed for being used with hardware acceleration. Because we could not
             support a web view class in a QGraphicsView unless it would be attached to a QGLWidget
             viewport, this feature is out of scope.
     \row
         \li QWebElement
-        \li Qt WebEngine uses a multi-process architecture and this means that
+        \li \QWE uses a multi-process architecture and this means that
             any access to the internal structure of the page has to be done
             asynchronously, any query result must be returned through callbacks.
             The QWebElement API was designed for synchronous access and this
             would require a complete redesign.
     \row
         \li QWebDatabase
-        \li The Web SQL Database feature that this API was wrapping in Qt WebKit
+        \li The Web SQL Database feature that this API was wrapping in Qt \WebKit
             was dropped from the HTML5 standard.
     \row
         \li QWebPluginDatabase, QWebPluginFactory, QWebPluginInfo, QWebPage::setPalette,
             QWebView::setRenderHints
-        \li Qt WebEngine renders web pages using Skia and is not using QPainter
+        \li \QWE renders web pages using Skia and is not using QPainter
             or Qt for this purpose. The HTML5 standard also now offers much
             better alternatives that were not available when native controls
-            plugins were introduced in Qt WebKit.
+            plugins were introduced in Qt \WebKit.
     \row
         \li QWebHistoryInterface
-        \li Visited links are persisted automatically by Qt WebEngine.
+        \li Visited links are persisted automatically by \QWE.
     \row
         \li QWebPage::setContentEditable
         \li In the latest HTML standard, any document element can be made editable through the
diff --git a/src/webenginewidgets/doc/src/qwebenginepage_lgpl.qdoc b/src/webenginewidgets/doc/src/qwebenginepage_lgpl.qdoc
index 517fdc7d9145a57f3eb6966996410c10095e7ac3..9aca48ebfc23559f7aa181f45bc155b95f90775f 100644
--- a/src/webenginewidgets/doc/src/qwebenginepage_lgpl.qdoc
+++ b/src/webenginewidgets/doc/src/qwebenginepage_lgpl.qdoc
@@ -438,7 +438,7 @@
 /*!
     \fn void QWebEnginePage::triggerAction(WebAction action, bool checked = false)
     This function can be called to trigger the specified \a action.
-    It is also called by Qt WebEngine if the user triggers the action, for example
+    It is also called by \QWE if the user triggers the action, for example
     through a context menu item.
 
     If \a action is a checkable action, then \a checked specifies whether the action
diff --git a/src/webenginewidgets/doc/src/qwebengineview_lgpl.qdoc b/src/webenginewidgets/doc/src/qwebengineview_lgpl.qdoc
index 568e7a63a14e761c36d857aceb872595f7b9f8be..fce1e8d8f41b110e641dc880f72db94a19755c6a 100644
--- a/src/webenginewidgets/doc/src/qwebengineview_lgpl.qdoc
+++ b/src/webenginewidgets/doc/src/qwebengineview_lgpl.qdoc
@@ -33,7 +33,7 @@
 
     \inmodule QtWebEngineWidgets
 
-    A \e {web view} is the main widget component of the Qt WebEngine web browsing module.
+    A \e {web view} is the main widget component of the \QWE web browsing module.
     It can be used in various applications to display web content live from the
     Internet.
 
@@ -129,7 +129,7 @@
 
     The HTML document is loaded immediately, whereas external objects are loaded asynchronously.
 
-    When using this method, Qt WebEngine assumes that external resources, such as
+    When using this method, \QWE assumes that external resources, such as
     JavaScript programs or style sheets, are encoded in UTF-8 unless otherwise
     specified. For example, the encoding of an external script can be specified
     through the \c charset attribute of the HTML script tag. Alternatively, the