summaryrefslogtreecommitdiffstats
path: root/src/doc/src/qt3d-overview.qdoc
diff options
context:
space:
mode:
Diffstat (limited to 'src/doc/src/qt3d-overview.qdoc')
-rw-r--r--src/doc/src/qt3d-overview.qdoc4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/doc/src/qt3d-overview.qdoc b/src/doc/src/qt3d-overview.qdoc
index c77265ed9..331f508e6 100644
--- a/src/doc/src/qt3d-overview.qdoc
+++ b/src/doc/src/qt3d-overview.qdoc
@@ -157,7 +157,7 @@
and the fragment's depth can be compared with the result of the sampling. If
the fragment is further away, then it is in shadow; otherwise it is lit.
- For example code, see the \l {Qt3D: Shadow Map QML Example}.
+ For example code, see the \l {Qt 3D: Shadow Map QML Example}.
\section2 Instanced Rendering
@@ -183,7 +183,7 @@
To combine support for both C++ and QML APIs with having a fully
configurable renderer, the concept of a \e framegraph was introduced. While
a \e scenegraph is a data-driven description of \e what to render, a \l
- {Qt 3D Renderer Framegraph}{framegraph} is a data-driven description of \e
+ {Qt 3D Render Framegraph}{framegraph} is a data-driven description of \e
how to render it.
A framegraph enables developers to choose between a simple forward renderer,