summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2013-02-01 22:30:12 (GMT)
committerRichard Purdie <richard.purdie@linuxfoundation.org>2013-02-14 17:24:01 (GMT)
commitc28948d9c3c021ba07665c869ff762e288a1621b (patch)
tree9b960d22b356cd10e6fa8bc4aff24a09bd4f614d
parent05e2c479d9bb859ea09c9465e604b201c00c0b45 (diff)
downloadpoky-c28948d9c3c021ba07665c869ff762e288a1621b.tar.gz
dev-manual: Various typos fixed
Received a patch from Robert P. J. Day but deleted it from my Thunderbird account so could not apply it directly. I applied most of his corrections. A couple I left alone. Reported-by: Robert P. J. Day <rpjday@crashcourse.ca> (From yocto-docs rev: 2cadd5265fcb5cc281c22ccae81260a6633229e2) 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-model.xml22
1 files changed, 11 insertions, 11 deletions
diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml
index 121519b..cdb799d 100644
--- a/documentation/dev-manual/dev-manual-model.xml
+++ b/documentation/dev-manual/dev-manual-model.xml
@@ -108,7 +108,7 @@
108 <orderedlist> 108 <orderedlist>
109 <listitem><para><emphasis>Set up your host development system to support 109 <listitem><para><emphasis>Set up your host development system to support
110 development using the Yocto Project</emphasis>: See the 110 development using the Yocto Project</emphasis>: See the
111 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>" 111 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>"
112 and the 112 and the
113 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both 113 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
114 in the Yocto Project Quick Start for requirements.</para></listitem> 114 in the Yocto Project Quick Start for requirements.</para></listitem>
@@ -119,7 +119,7 @@
119 process and to the tools you need. 119 process and to the tools you need.
120 For information on how to set up the 120 For information on how to set up the
121 <link linkend='source-directory'>Source Directory</link>, see the 121 <link linkend='source-directory'>Source Directory</link>, see the
122 "<link linkend='getting-setup'>Getting Setup</link>" section.</para></listitem> 122 "<link linkend='getting-setup'>Getting Set up</link>" section.</para></listitem>
123 <listitem><para><emphasis>Establish the <filename>meta-intel</filename> 123 <listitem><para><emphasis>Establish the <filename>meta-intel</filename>
124 repository on your system</emphasis>: Having local copies 124 repository on your system</emphasis>: Having local copies
125 of these supported BSP layers on your system gives you 125 of these supported BSP layers on your system gives you
@@ -255,7 +255,7 @@
255 <para> 255 <para>
256 Traditionally, when one thinks of a patched kernel, they think of a base kernel 256 Traditionally, when one thinks of a patched kernel, they think of a base kernel
257 source tree and a fixed structure that contains kernel patches. 257 source tree and a fixed structure that contains kernel patches.
258 The Yocto Project, however, employs mechanisms, that in a sense, result in a kernel source 258 The Yocto Project, however, employs mechanisms that, in a sense, result in a kernel source
259 generator. 259 generator.
260 By the end of this section, this analogy will become clearer. 260 By the end of this section, this analogy will become clearer.
261 </para> 261 </para>
@@ -338,7 +338,7 @@
338 Conceptually, you can think of the kernel source repositories as all the 338 Conceptually, you can think of the kernel source repositories as all the
339 source files necessary for all the supported kernels. 339 source files necessary for all the supported kernels.
340 As a developer, you are just interested in the source files for the kernel on 340 As a developer, you are just interested in the source files for the kernel on
341 on which you are working. 341 which you are working.
342 And, furthermore, you need them available on your host system. 342 And, furthermore, you need them available on your host system.
343 </para> 343 </para>
344 344
@@ -401,7 +401,7 @@
401 <orderedlist> 401 <orderedlist>
402 <listitem><para><emphasis>Set up your host development system to support 402 <listitem><para><emphasis>Set up your host development system to support
403 development using the Yocto Project</emphasis>: See 403 development using the Yocto Project</emphasis>: See
404 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>" and 404 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>" and
405 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both 405 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
406 in the Yocto Project Quick Start for requirements.</para></listitem> 406 in the Yocto Project Quick Start for requirements.</para></listitem>
407 <listitem><para><emphasis>Establish a local copy of project files on your 407 <listitem><para><emphasis>Establish a local copy of project files on your
@@ -455,7 +455,7 @@
455 Doing so, can produce unexpected results when the OpenEmbedded build system 455 Doing so, can produce unexpected results when the OpenEmbedded build system
456 regenerates the configuration file.</para> 456 regenerates the configuration file.</para>
457 <para>Once you are satisfied with the configuration changes made using 457 <para>Once you are satisfied with the configuration changes made using
458 <filename>menuconfig</filename>, you can directly examine the 458 <filename>menuconfig</filename>, you can directly compare the
459 <filename>.config</filename> file against a saved original and gather those 459 <filename>.config</filename> file against a saved original and gather those
460 changes into a config fragment to be referenced from within the kernel's 460 changes into a config fragment to be referenced from within the kernel's
461 <filename>.bbappend</filename> file.</para></listitem> 461 <filename>.bbappend</filename> file.</para></listitem>
@@ -513,11 +513,11 @@
513 <orderedlist> 513 <orderedlist>
514 <listitem><para><emphasis>Prepare the Host System for the Yocto Project</emphasis>: 514 <listitem><para><emphasis>Prepare the Host System for the Yocto Project</emphasis>:
515 See 515 See
516 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distributions</ulink>" and 516 "<ulink url='&YOCTO_DOCS_QS_URL;#the-linux-distro'>The Linux Distribution</ulink>" and
517 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both 517 "<ulink url='&YOCTO_DOCS_QS_URL;#packages'>The Packages</ulink>" sections both
518 in the Yocto Project Quick Start for requirements.</para></listitem> 518 in the Yocto Project Quick Start for requirements.</para></listitem>
519 <listitem><para><emphasis>Secure the Yocto Project Kernel Target Image</emphasis>: 519 <listitem><para><emphasis>Secure the Yocto Project Kernel Target Image</emphasis>:
520 You must have a target kernel image that has been built using the OpenEmbeded 520 You must have a target kernel image that has been built using the OpenEmbedded
521 build system.</para> 521 build system.</para>
522 <para>Depending on whether the Yocto Project has a pre-built image that matches your target 522 <para>Depending on whether the Yocto Project has a pre-built image that matches your target
523 architecture and where you are going to run the image while you develop your application 523 architecture and where you are going to run the image while you develop your application
@@ -527,7 +527,7 @@
527 <ulink url='&YOCTO_MACHINES_DL_URL;'><filename>machines</filename></ulink> 527 <ulink url='&YOCTO_MACHINES_DL_URL;'><filename>machines</filename></ulink>
528 if your target architecture is supported and you are going to develop 528 if your target architecture is supported and you are going to develop
529 and test your application on actual hardware.</para></listitem> 529 and test your application on actual hardware.</para></listitem>
530 <listitem><para>Download the image from the 530 <listitem><para>Download the image from
531 <ulink url='&YOCTO_QEMU_DL_URL;'> 531 <ulink url='&YOCTO_QEMU_DL_URL;'>
532 <filename>machines/qemu</filename></ulink> if your target architecture is supported 532 <filename>machines/qemu</filename></ulink> if your target architecture is supported
533 and you are going to develop and test your application using the QEMU 533 and you are going to develop and test your application using the QEMU
@@ -1485,7 +1485,7 @@ directory.</para></listitem>
1485 <listitem><para><emphasis>Develop and Test your Application:</emphasis> At this point, 1485 <listitem><para><emphasis>Develop and Test your Application:</emphasis> At this point,
1486 you have the tools to develop your application. 1486 you have the tools to develop your application.
1487 If you need to separately install and use the QEMU emulator, you can go to 1487 If you need to separately install and use the QEMU emulator, you can go to
1488 <ulink url='http://www.qemu.org'>QEMU Home Page</ulink> to download and learn about the 1488 <ulink url='http://wiki.qemu.org/Main_Page'>QEMU Home Page</ulink> to download and learn about the
1489 emulator.</para></listitem> 1489 emulator.</para></listitem>
1490 </orderedlist> 1490 </orderedlist>
1491 </para> 1491 </para>
@@ -1844,7 +1844,7 @@ directory.</para></listitem>
1844 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink> 1844 <ulink url='&YOCTO_DOCS_REF_URL;#var-MACHINE'><filename>MACHINE</filename></ulink>
1845 for which you are building the image.</para></listitem> 1845 for which you are building the image.</para></listitem>
1846 <listitem><para>You can modify various policy settings such as the package format used to build with, 1846 <listitem><para>You can modify various policy settings such as the package format used to build with,
1847 the parrallelism BitBake uses, whether or not to build an external toolchain, and which host 1847 the parallelism BitBake uses, whether or not to build an external toolchain, and which host
1848 to build against.</para></listitem> 1848 to build against.</para></listitem>
1849 <listitem><para>You can manage 1849 <listitem><para>You can manage
1850 <link linkend='understanding-and-creating-layers'>layers</link>.</para></listitem> 1850 <link linkend='understanding-and-creating-layers'>layers</link>.</para></listitem>