diff --git a/documentation/yocto-project-qs/yocto-project-qs.xml b/documentation/yocto-project-qs/yocto-project-qs.xml index 141e13fad8..e7b83b2f64 100644 --- a/documentation/yocto-project-qs/yocto-project-qs.xml +++ b/documentation/yocto-project-qs/yocto-project-qs.xml @@ -476,7 +476,7 @@ - Install the stand-alone Yocto toolchain tarball. + Install the appropriate stand-alone Yocto toolchain tarball. Download the pre-built image that will boot with QEMU. You need to be sure to get the QEMU image that matches your target machine’s architecture (e.g. x86, ARM, etc.). @@ -493,7 +493,7 @@ script and support files, from the appropriate directory under . Toolchains are available for 32-bit and 64-bit development systems from the - i686 and x86_64 directories, respectively. + i686 and x86-64 directories, respectively. Each type of development system supports five target architectures. The tarball files are named such that a string representing the host system appears first in the filename and then is immediately followed by a string representing @@ -501,7 +501,7 @@ - poky-eglibc<host_system>-<arch>-toolchain-gmae-<release>.tar.bz2 + poky-eglibc-<host_system>-<arch>-toolchain-gmae-<release>.tar.bz2 Where: <host_system> is a string representing your development system: @@ -554,7 +554,7 @@ Be sure to use the kernel that matches the architecture you want to simulate. Download areas exist for the five supported machine architectures: qemuarm, qemumips, qemuppc, - qemux86, and qemux86_64. + qemux86, and qemux86-64. @@ -651,7 +651,7 @@ that the kernel and filesystem are for a 32-bit target architecture. $ source &YOCTO_ADTPATH_DIR;/environment-setup-i686-poky-linux - $ runqemu qemux86 bzImage-3.0-qemux86-&DISTRO;.bin \ + $ runqemu qemux86 bzImage-qemux86-&DISTRO;.bin \ core-image-sato-qemux86.ext3