documentation/poky-ref-manual: Minor wording fixes

Robert identified several wording issues.  Fixes applied.

(From yocto-docs rev: 9c1ed58a1ecdd620246970419ed58b53f95cf2ec)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

2 files changed, 6 insertions, 6 deletions

diff --git a/documentation/poky-ref-manual/introduction.xml b/documentation/poky-ref-manual/introduction.xml
index 52cb4d6..492af71 100644
--- a/documentation/poky-ref-manual/introduction.xml
+++ b/documentation/poky-ref-manual/introduction.xml
@@ -89,7 +89,7 @@
 <section id='intro-requirements'>
 <title>System Requirements</title>
     <para>
-        For system Yocto Project system requirements, see the 
+        For Yocto Project system requirements, see the
         <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html#resources'>
         What You Need and How You Get It</ulink> section in the 
         <ulink url='http://www.yoctoproject.org/docs/1.1/yocto-project-qs/yocto-project-qs.html'>
diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml
index 7b24841..70573ef 100644
--- a/documentation/poky-ref-manual/usingpoky.xml
+++ b/documentation/poky-ref-manual/usingpoky.xml
@@ -16,7 +16,7 @@
         The BitBake task executor together with various types of configuration files form the 
         Yocto Project core.
         This section overviews the BitBake task executor and the
-        configuration files by describing what they are used for and they they interact.
+        configuration files by describing what they are used for and how they interact.
     </para>
     
     <para>  
@@ -29,7 +29,7 @@
             information (e.g. how to build a Linux kernel).</para></listitem>
         <listitem><para><emphasis>Configuration Data:</emphasis>  Defines machine-specific settings, 
             policy decisions, etc.
-            Configuration data acts a the glue to bind everything together.</para></listitem>
+            Configuration data acts as the glue to bind everything together.</para></listitem>
     </itemizedlist>
         For more information on data, see the
         <ulink url='http://www.yoctoproject.org/docs/1.1/dev-manual/dev-manual.html#yocto-project-terms'>
@@ -164,7 +164,7 @@
         The first thing you need to do is set up the Yocto Project build environment by sourcing
         the environment setup script as follows:
         <literallayout class='monospaced'>
-     $ source oe-init-build-env [build_dir];
+     $ source oe-init-build-env [build_dir]
         </literallayout>
     </para>
 
@@ -172,7 +172,7 @@
         The <filename>build_dir</filename> is optional and specifies the directory Yocto Project
         uses for the build.
         If you do not specify a build directory it defaults to <filename>build</filename>
-        in the Yocto Project files directory structure.
+        in your current working directory.
         A common practice is to use a different build directory for different targets. 
         For example, <filename>~/build/x86</filename> for a <filename>qemux86</filename>
         target, and <filename>~/build/arm</filename> for a <filename>qemuarm</filename> target.
@@ -310,7 +310,7 @@
             You can view a list of tasks in a given package by running the
             <filename>listtasks</filename> task as follows:
             <literallayout class='monospaced'>
-     $ bitbake matchbox-desktop -c
+     $ bitbake matchbox-desktop -c listtasks
             </literallayout>
             The results are in the file <filename>${WORKDIR}/temp/log.do_listtasks</filename>.
         </para>