summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-04-09 11:05:03 -0700
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-04-10 16:20:55 +0100
commitd8f9811fa321a11f93c95d12f4097f351d97d5e6 (patch)
treeed5a50e506cb70f465078e5ab55f454440a20255
parent29148bc39a9038239c50ac8b7690be99e535441e (diff)
downloadpoky-d8f9811fa321a11f93c95d12f4097f351d97d5e6.tar.gz
dev-manual: Spelling checks for Chapter 2.
(From yocto-docs rev: 9a190d74ed169400a2f37e47738e00d4b191b285) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
-rw-r--r--documentation/dev-manual/dev-manual-start.xml4
1 files changed, 2 insertions, 2 deletions
diff --git a/documentation/dev-manual/dev-manual-start.xml b/documentation/dev-manual/dev-manual-start.xml
index fb95d07377..719d0f3919 100644
--- a/documentation/dev-manual/dev-manual-start.xml
+++ b/documentation/dev-manual/dev-manual-start.xml
@@ -297,7 +297,7 @@
297 a centralized tarball download directory through the 297 a centralized tarball download directory through the
298 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'>DL_DIR</ulink></filename> variable.</para></listitem> 298 <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DL_DIR'>DL_DIR</ulink></filename> variable.</para></listitem>
299 <listitem><para>Build the image using the <filename>bitbake</filename> command. 299 <listitem><para>Build the image using the <filename>bitbake</filename> command.
300 If you want information on BitBake, see the user manual inculded in the 300 If you want information on BitBake, see the user manual included in the
301 <filename>bitbake/doc/manual</filename> directory of the 301 <filename>bitbake/doc/manual</filename> directory of the
302 <link linkend='source-directory'>Source Directory</link>.</para></listitem> 302 <link linkend='source-directory'>Source Directory</link>.</para></listitem>
303 <listitem><para>Run the image either on the actual hardware or using the QEMU 303 <listitem><para>Run the image either on the actual hardware or using the QEMU
@@ -333,7 +333,7 @@
333 Regardless of the type of image you are using, you need to download the pre-built kernel 333 Regardless of the type of image you are using, you need to download the pre-built kernel
334 that you will boot in the QEMU emulator and then download and extract the target root 334 that you will boot in the QEMU emulator and then download and extract the target root
335 filesystem for your target machine’s architecture. 335 filesystem for your target machine’s architecture.
336 You can get architecture-specific binaries and filesystems from 336 You can get architecture-specific binaries and file systems from
337 <ulink url='&YOCTO_MACHINES_DL_URL;'>machines</ulink>. 337 <ulink url='&YOCTO_MACHINES_DL_URL;'>machines</ulink>.
338 You can get installation scripts for stand-alone toolchains from 338 You can get installation scripts for stand-alone toolchains from
339 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'>toolchains</ulink>. 339 <ulink url='&YOCTO_TOOLCHAIN_DL_URL;'>toolchains</ulink>.