From a8a25047c79ac7914a3496464ec5f0484fc26952 Mon Sep 17 00:00:00 2001 From: "Robert P. J. Day" Date: Wed, 2 Nov 2011 13:37:32 -0700 Subject: documentation/dev-manual/dev-manual-model.xml: Robert P. J. Day Edits Two small corrections for better wording. A mis-spelling also fixed. (From yocto-docs rev: 915ec9f9adbde86008ffb086ac81a435d5910733) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/dev-manual/dev-manual-model.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'documentation') diff --git a/documentation/dev-manual/dev-manual-model.xml b/documentation/dev-manual/dev-manual-model.xml index 93406eb600..1d45a036c8 100644 --- a/documentation/dev-manual/dev-manual-model.xml +++ b/documentation/dev-manual/dev-manual-model.xml @@ -35,8 +35,8 @@ System development involves modification or creation of an image that you want to run on a specific hardware target. Usually, when you want to create an image that runs on embedded hardware, the image does - not require the same amount of features that a full-fledged Linux distribution provides. - Thus, you can create a much smaller image that is designed to just use the hardware + not require the same number of features that a full-fledged Linux distribution provides. + Thus, you can create a much smaller image that is designed to use only the hardware features for your particular hardware. @@ -213,8 +213,8 @@ Traditionally, when one thinks of a patched kernel, they think of a base kernel - source tree and a fixed structure that conains kernel patches. - The Yocto Project, however, employs mechanisims, that in a sense, result in a kernel source + source tree and a fixed structure that contains kernel patches. + The Yocto Project, however, employs mechanisms, that in a sense, result in a kernel source generator. By the end of this section, this analogy will become clearer. -- cgit v1.2.3-54-g00ecf