yocto-project-qs: Minor edits for readability

(From yocto-docs rev: 089c6e1392e6376e1e73f3ded74c40c60bee1109)

Signed-off-by: Scott Rifenbark <srifenbark@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
This commit is contained in:
Scott Rifenbark 2017-10-17 08:34:27 -07:00 committed by Richard Purdie
parent a4f6e19e37
commit ff7aa3dd43

View File

@ -427,9 +427,9 @@
If your build host is using a Poky container, you can
use the same Git commands.
</note>
The example clones the <filename>poky</filename> repository
and then checks out the latest Yocto Project Release by tag
(i.e. <filename>&DISTRO_REL_TAG;</filename>):
The following example clones the <filename>poky</filename>
repository and then checks out the latest Yocto Project Release
by tag (i.e. <filename>&DISTRO_REL_TAG;</filename>):
<literallayout class='monospaced'>
$ git clone git://git.yoctoproject.org/poky
Cloning into 'poky'...
@ -456,8 +456,10 @@
Rather than checking out the entire development branch
of a release (i.e. the tip), which could be continuously
changing while you are doing your development, you would
check out a branch based on a release tag. Doing so
provides you with an unchanging, stable set of files.
check out a branch based on a release tag as shown in
the previous example.
Doing so provides you with an unchanging, stable set of
files.
</note>
</para>
@ -479,7 +481,8 @@
your images.
<note>
A graphical user interface to the Yocto Project is available
through Toaster.
through
<ulink url='&YOCTO_DOCS_REF_URL;#toaster-term'>Toaster</ulink>.
See the
<ulink url='&YOCTO_DOCS_TOAST_URL;'>Toaster User Manual</ulink>
for more information.
@ -518,31 +521,32 @@
Use the following commands to build your image.
The OpenEmbedded build system creates an entire Linux
distribution, including the toolchain, from source.
<note><title>Note about Network Proxies</title>
<para>
By default, the build process searches for source code
using a pre-determined order through a set of
locations.
If you are working behind a firewall and your build
host is not set up for proxies, you could encounter
problems with the build process when fetching source
code (e.g. fetcher failures or Git failures).
</para>
<para>
If you do not know your proxy settings, consult your
local network infrastructure resources and get that
information.
A good starting point could also be to check your web
browser settings.
Finally, you can find more information on using the
Yocto Project behind a firewall in the Yocto Project
Reference Manual
<ulink url='&YOCTO_DOCS_REF_URL;#how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>FAQ</ulink>
and on the
"<ulink url='https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy'>Working Behind a Network Proxy</ulink>"
wiki page.
</para>
<note><title>Notes about Network Proxies</title>
<itemizedlist>
<listitem><para>
By default, the build process searches for source
code using a pre-determined order through a set of
locations.
If you are working behind a firewall and your build
host is not set up for proxies, you could encounter
problems with the build process when fetching source
code (e.g. fetcher failures or Git failures).
</para></listitem>
<listitem><para>
If you do not know your proxy settings, consult your
local network infrastructure resources and get that
information.
A good starting point could also be to check your
web browser settings.
Finally, you can find more information on using the
Yocto Project behind a firewall in the Yocto Project
Reference Manual
<ulink url='&YOCTO_DOCS_REF_URL;#how-does-the-yocto-project-obtain-source-code-and-will-it-work-behind-my-firewall-or-proxy-server'>FAQ</ulink>
and on the
"<ulink url='https://wiki.yoctoproject.org/wiki/Working_Behind_a_Network_Proxy'>Working Behind a Network Proxy</ulink>"
wiki page.
</para></listitem>
</itemizedlist>
</note>
</para>