documentation/dev-manual/dev-manual-start.xml: Robert P. J. Edits

Robert isolated a few technical errors and made some other wording
suggestions.  I took the technical corrections and modified one
of his suggested wording changes.

(From yocto-docs rev: 3c6bbae05cdf2265e04d967050354ce75d62b4e2)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Robert P. J. Day 2011-11-02 13:05:20 -07:00 committed by Richard Purdie
parent 9f103615fb
commit 54956b8d50
1 changed files with 4 additions and 4 deletions

View File

@ -36,7 +36,7 @@
While the Yocto Project does not provide a strict testing framework,
it does provide or generate for you artifacts that let you perform target-level and
emulated testing and debugging.
And, if you are an <trademark class='trade'>Eclipse</trademark>
Additionally, if you are an <trademark class='trade'>Eclipse</trademark>
IDE user, you can install an Eclipse Yocto Plug-in to allow you to
develop within that familiar environment.
</para>
@ -77,7 +77,7 @@
Once you have the tarball, just extract it into a directory of your choice.</para>
<para>For example, the following command extracts the Yocto Project 1.1 release tarball
into the current working directory and sets up the Yocto Project file structure
with a top-level directory named <filename>poky-1.1</filename>:
with a top-level directory named <filename>poky-edison-6.0</filename>:
<literallayout class='monospaced'>
$ tar xfj poky-edison-6.0.tar.bz2
</literallayout></para>
@ -195,7 +195,7 @@
<filename>meta-intel</filename>
Git repository inside the <filename>poky</filename> Git repository.
<literallayout class='monospaced'>
$cd poky
$ cd poky
$ git clone git://git.yoctoproject.org/meta-intel.git
Initialized empty Git repository in /home/scottrif/poky/meta-intel/.git/
remote: Counting objects: 1325, done.
@ -240,7 +240,7 @@
<listitem><para>Optionally ensure the <filename>conf/local.conf</filename> configuration file is set
up how you want it.
This file defines the target machine architecture and other build options.</para></listitem>
<listitem><para>Build the image using the BitBake command.
<listitem><para>Build the image using the <command>bitbake</command> command.
If you want information on Bitbake, see the user manual at
<ulink url='http://docs.openembedded.org/bitbake/html'></ulink>.</para></listitem>
<listitem><para>Run the image either on the actual hardware or using the QEMU