diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index 02e77e8dd6..b533e0d281 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -2691,14 +2691,14 @@ the details.
 
             <para>
                 To use the <filename>menuconfig</filename> tool in the Yocto Project development
-                environment, you must build the tool using BitBake.
+                environment, you must launch it using BitBake.
                 Thus, the environment must be set up using the
                 <ulink url='&YOCTO_DOCS_REF_URL;#structure-core-script'><filename>&OE_INIT_FILE;</filename></ulink>
                 or
                 <ulink url='&YOCTO_DOCS_REF_URL;#structure-memres-core-script'><filename>oe-init-build-env-memres</filename></ulink>
                 script found in the
                 <link linkend='build-directory'>Build Directory</link>.
-                The following commands build and invoke <filename>menuconfig</filename> assuming the
+                The following commands run <filename>menuconfig</filename> assuming the
                 <link linkend='source-directory'>Source Directory</link>
                 top-level folder is <filename>~/poky</filename>:
                 <literallayout class='monospaced'>
@@ -2720,7 +2720,7 @@ the details.
                 Thus, the following commands from the shell in which you previously sourced the
                 environment initialization script cleans the shared state cache and the
                 <ulink url='&YOCTO_DOCS_REF_URL;#var-WORKDIR'><filename>WORKDIR</filename></ulink>
-                directory and then builds and launches <filename>menuconfig</filename>:
+                directory and then runs <filename>menuconfig</filename>:
                 <literallayout class='monospaced'>
      $ bitbake linux-yocto -c menuconfig
                 </literallayout>