dev-manual: Various fixes for links, typos, and grammar

1. Added "Debian" as a distribution for best results.
2. Fixed a link to the Hob page and two links for the
   Build Appliance.
3. Three typos fixed and a few grammar items fixed.

(From yocto-docs rev: 0b381094ed9cc2d66895d4ad7c63005c8a918eb1)

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 2012-12-26 08:24:41 -06:00 committed by Richard Purdie
parent 30c0c9e358
commit 4c582a8b2e
3 changed files with 11 additions and 11 deletions

View File

@ -119,15 +119,15 @@
Release Notes</ulink>:</emphasis> Features, updates and known issues for the current Release Notes</ulink>:</emphasis> Features, updates and known issues for the current
release of the Yocto Project.</para></listitem> release of the Yocto Project.</para></listitem>
<listitem><para><emphasis> <listitem><para><emphasis>
<ulink url='&YOCTO_HOME_URL;/projects/hob'> <ulink url='&YOCTO_HOME_URL;/tools-resources/projects/hob'>
Hob</ulink>:</emphasis> A graphical user interface for BitBake. Hob</ulink>:</emphasis> A graphical user interface for BitBake.
Hob's primary goal is to enable a user to perform common tasks more easily.</para></listitem> Hob's primary goal is to enable a user to perform common tasks more easily.</para></listitem>
<listitem><para><emphasis> <listitem><para><emphasis>
<ulink url='&YOCTO_HOME_URL;/documentation/build-appliance'> <ulink url='&YOCTO_HOME_URL;/download/build-appliance-0'>
Build Appliance</ulink>:</emphasis> A bootable custom embedded Linux image you can Build Appliance</ulink>:</emphasis> A bootable custom embedded Linux image you can
either build using a non-Linux development system (VMware applications) or download either build using a non-Linux development system (VMware applications) or download
from the Yocto Project website. from the Yocto Project website.
See the <ulink url='&YOCTO_HOME_URL;/documentation/build-appliance'>Build Appliance</ulink> See the <ulink url='&YOCTO_HOME_URL;/documentation/build-appliance-manual'>Build Appliance</ulink>
page for more information.</para></listitem> page for more information.</para></listitem>
<listitem><para><emphasis> <listitem><para><emphasis>
<ulink url='&YOCTO_BUGZILLA_URL;'>Bugzilla</ulink>:</emphasis> <ulink url='&YOCTO_BUGZILLA_URL;'>Bugzilla</ulink>:</emphasis>

View File

@ -97,7 +97,7 @@
<para> <para>
Most teams have many pieces of software undergoing active development at any given time. Most teams have many pieces of software undergoing active development at any given time.
You can derive large benefits by putting these pieces under the control of a source You can derive large benefits by putting these pieces under the control of a source
control system that is compatible (i.e. Git or Subversion (SVN)) with the OpenEmbeded control system that is compatible (i.e. Git or Subversion (SVN)) with the OpenEmbedded
build system that the Yocto Project uses. build system that the Yocto Project uses.
You can then set the autobuilder to pull the latest revisions of the packages You can then set the autobuilder to pull the latest revisions of the packages
and test the latest commits by the builds. and test the latest commits by the builds.
@ -131,7 +131,7 @@
<listitem><para>Maintain your metadata in layers that make sense <listitem><para>Maintain your metadata in layers that make sense
for your situation. for your situation.
See the "<link linkend='understanding-and-creating-layers'>Understanding See the "<link linkend='understanding-and-creating-layers'>Understanding
and Creating Layeres</link>" section for more information on and Creating Layers</link>" section for more information on
layers.</para></listitem> layers.</para></listitem>
<listitem><para>Separate the project's metadata and code by using <listitem><para>Separate the project's metadata and code by using
separate Git repositories. separate Git repositories.
@ -187,7 +187,7 @@
</para> </para>
<para> <para>
Once you are set up through either tarball extraction or creation of Git repositories, Once you are set up through either tarball extraction or a checkout of Git repositories,
you are ready to develop. you are ready to develop.
</para> </para>
@ -362,7 +362,7 @@
In its most general sense, it is an open-source project that was initially developed In its most general sense, it is an open-source project that was initially developed
by OpenedHand. With OpenedHand, poky was developed off of the existing OpenEmbedded by OpenedHand. With OpenedHand, poky was developed off of the existing OpenEmbedded
build system becoming a build system for embedded images. build system becoming a build system for embedded images.
After Intel Corporation aquired OpenedHand, the project poky became the basis for After Intel Corporation acquired OpenedHand, the project poky became the basis for
the Yocto Project's build system. the Yocto Project's build system.
Within the Yocto Project source repositories, poky exists as a separate Git repository Within the Yocto Project source repositories, poky exists as a separate Git repository
that can be cloned to yield a local copy on the host system. that can be cloned to yield a local copy on the host system.
@ -380,7 +380,7 @@
and unpacking a Yocto Project release tarball or creating a local copy of and unpacking a Yocto Project release tarball or creating a local copy of
the <filename>poky</filename> Git repository the <filename>poky</filename> Git repository
<filename>git://git.yoctoproject.org/poky</filename>. <filename>git://git.yoctoproject.org/poky</filename>.
Sometimes you might here the term "poky directory" used to refer to this Sometimes you might hear the term "poky directory" used to refer to this
directory structure. directory structure.
<note> <note>
The OpenEmbedded build system does not support file or directory names that The OpenEmbedded build system does not support file or directory names that
@ -422,7 +422,7 @@
reflects the exact copy of the files at the time of their release. reflects the exact copy of the files at the time of their release.
You do this by using Git tags that are part of the repository.</para> You do this by using Git tags that are part of the repository.</para>
<para>For more information on concepts around Git repositories, branches, and tags, <para>For more information on concepts related to Git repositories, branches, and tags,
see the see the
"<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>" "<link linkend='repositories-tags-and-branches'>Repositories, Tags, and Branches</link>"
section.</para></listitem> section.</para></listitem>

View File

@ -53,7 +53,7 @@
<listitem><para><emphasis>Host System:</emphasis> You should have a reasonably current <listitem><para><emphasis>Host System:</emphasis> You should have a reasonably current
Linux-based host system. Linux-based host system.
You will have the best results with a recent release of Fedora, You will have the best results with a recent release of Fedora,
OpenSUSE, Ubuntu, or CentOS as these releases are frequently tested against the Yocto Project OpenSUSE, Debian, Ubuntu, or CentOS as these releases are frequently tested against the Yocto Project
and officially supported. and officially supported.
For a list of the distributions under validation and their status, see the For a list of the distributions under validation and their status, see the
"<ulink url='&YOCTO_DOCS_REF_URL;#detailed-supported-distros'>Supported Linux Distributions</ulink>" section "<ulink url='&YOCTO_DOCS_REF_URL;#detailed-supported-distros'>Supported Linux Distributions</ulink>" section
@ -70,7 +70,7 @@
for the supported distributions.</para></listitem> for the supported distributions.</para></listitem>
<listitem id='local-yp-release'><para><emphasis>Yocto Project Release:</emphasis> <listitem id='local-yp-release'><para><emphasis>Yocto Project Release:</emphasis>
You need a release of the Yocto Project. You need a release of the Yocto Project.
You set up a with local <link linkend='source-directory'>Source Directory</link> You set that up with a local <link linkend='source-directory'>Source Directory</link>
one of two ways depending on whether you one of two ways depending on whether you
are going to contribute back into the Yocto Project or not. are going to contribute back into the Yocto Project or not.
<note> <note>