aboutsummaryrefslogtreecommitdiffstats
path: root/documentation/poky-ref-manual
diff options
context:
space:
mode:
authorScott Rifenbark <scott.m.rifenbark@intel.com>2011-03-17 17:59:59 -0600
committerRichard Purdie <richard.purdie@linuxfoundation.org>2011-03-18 17:20:45 +0000
commitbb6fbb484ec912aabca77fd4d124c97fc7f956e1 (patch)
tree4384d0396fc602702d26b975ce0300df17f0a343 /documentation/poky-ref-manual
parent9cfed91ee7c0a619e52abc098c20d6ed8b69416b (diff)
downloadopenembedded-core-contrib-bb6fbb484ec912aabca77fd4d124c97fc7f956e1.tar.gz
documentation/poky-ref-manual/usingpoky.xml: Small edits
I made some minor edits. Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Diffstat (limited to 'documentation/poky-ref-manual')
-rw-r--r--documentation/poky-ref-manual/usingpoky.xml8
1 files changed, 4 insertions, 4 deletions
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 @@
<para>
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:
</para>
<section id='usingpoky-debugging-taskfailures'>