aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/ref-manual/introduction.xml
diff options
context:
space:
mode:
authorRobert P. J. Day <rpjday@crashcourse.ca>2013-11-05 10:34:12 -0800
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-12-03 12:53:02 +0000
commita8388ac9f59f7710ac5c6635a32ec37cce2046d3 (patch)
treedd47b058f9464f1dd9d50e11662dc62574d3cad5 /documentation/ref-manual/introduction.xml
parentae7c4d5626a63b542caf10234332e44c9f66555a (diff)
downloadopenembedded-core-contrib-a8388ac9f59f7710ac5c6635a32ec37cce2046d3.tar.gz
ref-manual: Small number of fixes to Ch1 of ref-manual
Three chunks attempted in a patch from Robert. Two out of three worked. One did not because the text had changed due to re-writing a note that had some links to out-of-date wiki pages. (From yocto-docs rev: 7f807d6df4842d47534c4011ccf67fd01bf0b830) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation/ref-manual/introduction.xml')
-rw-r--r--documentation/ref-manual/introduction.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/ref-manual/introduction.xml b/documentation/ref-manual/introduction.xml
index ab53cf5da9..19a1fcc7e0 100644
--- a/documentation/ref-manual/introduction.xml
+++ b/documentation/ref-manual/introduction.xml
@@ -246,11 +246,11 @@
</section>
<section id='opensuse-packages'>
- <title>OpenSUSE Packages</title>
+ <title>openSUSE Packages</title>
<para>
The following list shows the required packages by function
- given a supported OpenSUSE Linux distribution:
+ given a supported openSUSE Linux distribution:
<itemizedlist>
<listitem><para><emphasis>Essentials:</emphasis>
Packages needed to build an image for a headless
@@ -341,8 +341,8 @@
you can resolve this by either downloading a pre-built tarball
containing these tools, or building such a tarball on another
system.
- Regardless of the method, once you have the tarball you simply
- install it somewhere on you system, such as a directory in your
+ Regardless of the method, once you have the tarball, you simply
+ install it somewhere on your system, such as a directory in your
home directory, and then source the environment script provided,
which adds the tools into <filename>PATH</filename> and sets
any other environment variables required to run the tools.