|author||Bill Traynor <email@example.com>||2013-06-19 14:30:40 -0400|
|committer||Richard Purdie <firstname.lastname@example.org>||2014-01-13 22:00:29 +0000|
user-manual-hello.xml: Fixed up some bad formatting.
Fixed some bad line breaks and whitespace. Signed-off-by: Bill Traynor <email@example.com>
1 files changed, 14 insertions, 16 deletions
diff --git a/doc/user-manual/user-manual-hello.xml b/doc/user-manual/user-manual-hello.xml
index cc2a0f16..41054872 100644
@@ -19,10 +19,10 @@
- <para>Please refer to Chapter 1 Section 1.7 for the various methods to obtain
- Once the source code is on your machine the BitBake directory will appear as
+ <para>Please refer to Chapter 1 Section 1.7 for the various methods to
+ obtain BitBake.
+ Once the source code is on your machine the BitBake directory will
+ appear as follows:
$ ls -al
@@ -50,27 +50,25 @@
a directory and it should match the directory tree above.
Please note that you'll see your username wherever
"wmat" appears above.
- <title>Setting Up BitBake</title>
- <para>Now let's setup our BitBake environment.
- The recommended method is to run BitBake from a
- directory of your choice.
- The directory can be within your home directory or in
- /usr/local, depending on your preference.
- Let's run BitBake now to make sure it's working.
- From the BitBake source code directory issue
- the following command:
+ <title>Setting Up the BitBake Environment</title>
+ <para>The recommended method to run BitBake is from a directory of your
+ The directory can be within your home directory or in /usr/local,
+ depending on your preference.
+ Let's run BitBake now to make sure it's working.
+ From the BitBake source code directory issue the following command:
<screen>$ ./bin/bitbake --version
BitBake Build Tool Core version 1.19.0, bitbake version
You're now ready to use BitBake.
- <para>Note that if you're a Vim user, you will find useful
+ <para>Note that if you're a Vim user, you will find useful
Vim configuration contributions in the