1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml
index 319795f672..ee08831c42 100644
--- a/documentation/ref-manual/technical-details.xml
+++ b/documentation/ref-manual/technical-details.xml
@@ -442,11 +442,11 @@
            works on a per-task basis rather than a per-recipe basis.
            You might wonder why using a per-task basis is preferred over a per-recipe basis.
            To help explain, consider having the IPK packaging backend enabled and then switching to DEB.
-            In this case,
+            In this case, the
            <link linkend='ref-tasks-install'><filename>do_install</filename></link>
            and
            <link linkend='ref-tasks-package'><filename>do_package</filename></link>
-            outputs are still valid.
+            task outputs are still valid.
            However, with a per-recipe approach, the build would not include the
            <filename>.deb</filename> files.
            Consequently, you would have to invalidate the whole build and rerun it.

diff --git a/documentation/ref-manual/technical-details.xml b/documentation/ref-manual/technical-details.xml index 319795f672..ee08831c42 100644 --- a/documentation/ref-manual/technical-details.xml +++ b/documentation/ref-manual/technical-details.xml
@@ -442,11 +442,11 @@
442	works on a per-task basis rather than a per-recipe basis.	442	works on a per-task basis rather than a per-recipe basis.
443	You might wonder why using a per-task basis is preferred over a per-recipe basis.	443	You might wonder why using a per-task basis is preferred over a per-recipe basis.
444	To help explain, consider having the IPK packaging backend enabled and then switching to DEB.	444	To help explain, consider having the IPK packaging backend enabled and then switching to DEB.
445	In this case,	445	In this case, the
446	<link linkend='ref-tasks-install'><filename>do_install</filename></link>	446	<link linkend='ref-tasks-install'><filename>do_install</filename></link>
447	and	447	and
448	<link linkend='ref-tasks-package'><filename>do_package</filename></link>	448	<link linkend='ref-tasks-package'><filename>do_package</filename></link>
449	outputs are still valid.	449	task outputs are still valid.
450	However, with a per-recipe approach, the build would not include the	450	However, with a per-recipe approach, the build would not include the
451	<filename>.deb</filename> files.	451	<filename>.deb</filename> files.
452	Consequently, you would have to invalidate the whole build and rerun it.	452	Consequently, you would have to invalidate the whole build and rerun it.