summaryrefslogtreecommitdiffstats
path: root/src/webengine/doc/src/qtwebengine-debugging.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'src/webengine/doc/src/qtwebengine-debugging.qdoc')
-rw-r--r--src/webengine/doc/src/qtwebengine-debugging.qdoc12
1 files changed, 6 insertions, 6 deletions
diff --git a/src/webengine/doc/src/qtwebengine-debugging.qdoc b/src/webengine/doc/src/qtwebengine-debugging.qdoc
index b8b004095..088db5f87 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>