summaryrefslogtreecommitdiff
path: root/poky/documentation/overview-manual/concepts.rst
diff options
context:
space:
mode:
Diffstat (limited to 'poky/documentation/overview-manual/concepts.rst')
-rw-r--r--poky/documentation/overview-manual/concepts.rst4
1 files changed, 2 insertions, 2 deletions
diff --git a/poky/documentation/overview-manual/concepts.rst b/poky/documentation/overview-manual/concepts.rst
index 3017637529..89a5eb49fb 100644
--- a/poky/documentation/overview-manual/concepts.rst
+++ b/poky/documentation/overview-manual/concepts.rst
@@ -1200,7 +1200,7 @@ usually made available in the form of a shared state (sstate) cache.
:term:`SSTATE_MIRRORS`
variables.
-The idea of a setscene task (i.e ``do_``\ taskname\ ``_setscene``) is a
+The idea of a setscene task (i.e ``do_taskname_setscene``) is a
version of the task where instead of building something, BitBake can
skip to the end result and simply place a set of files into specific
locations as needed. In some cases, it makes sense to have a setscene
@@ -1614,7 +1614,7 @@ them if they are deemed to be valid.
section in the Yocto Project Development Tasks Manual.
- The code in the build system that supports incremental builds is
- not simple code. For techniques that help you work around issues
+ complex. For techniques that help you work around issues
related to shared state code, see the
":ref:`dev-manual/common-tasks:viewing metadata used to create the input signature of a shared state task`"
and