From 8e05ccaa0bde44b870908d4bb1f6dfbfdd2459e2 Mon Sep 17 00:00:00 2001 From: Scott Rifenbark Date: Thu, 17 Mar 2011 17:59:59 -0600 Subject: documentation/poky-ref-manual/usingpoky.xml: Small edits I made some minor edits. (From OE-Core rev: bb6fbb484ec912aabca77fd4d124c97fc7f956e1) Signed-off-by: Scott Rifenbark Signed-off-by: Richard Purdie --- documentation/poky-ref-manual/usingpoky.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'documentation/poky-ref-manual/usingpoky.xml') diff --git a/documentation/poky-ref-manual/usingpoky.xml b/documentation/poky-ref-manual/usingpoky.xml index 2782e2b856..75932665a3 100644 --- a/documentation/poky-ref-manual/usingpoky.xml +++ b/documentation/poky-ref-manual/usingpoky.xml @@ -183,12 +183,12 @@ The exact method for debugging Poky depends on the nature of the problem and on the system's area from which the bug originates. - Standard debugging practises such as comparison against the last - known working version with examination of the changes and the reapplication of steps + Standard debugging practices such as comparison against the last + known working version with examination of the changes and the re-application of steps to identify the one causing the problem are valid for Poky just as they are for any other system. - It's impossible to detail every possible potential failure but here are some general - tips to aid in debugging: + Even though it is impossible to detail every possible potential failure, + here are some general tips to aid in debugging:
-- cgit v1.2.3-54-g00ecf