summaryrefslogtreecommitdiffstats
path: root/documentation
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 18:00:09 +0000
commitb37e6a22342cb0567ec7fd1b8aed6c2daac85893 (patch)
tree22f1a6fe526efd07636eccc92aa56e509c10e75e /documentation
parentf32ea8feff88c9d01d4673bea932cd3b77492131 (diff)
downloadpoky-b37e6a22342cb0567ec7fd1b8aed6c2daac85893.tar.gz
documentation/poky-ref-manual/usingpoky.xml: Small edits
I made some minor edits. (From OE-Core rev: bb6fbb484ec912aabca77fd4d124c97fc7f956e1) Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'documentation')
-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 @@
183 <para> 183 <para>
184 The exact method for debugging Poky depends on the nature of the 184 The exact method for debugging Poky depends on the nature of the
185 problem and on the system's area from which the bug originates. 185 problem and on the system's area from which the bug originates.
186 Standard debugging practises such as comparison against the last 186 Standard debugging practices such as comparison against the last
187 known working version with examination of the changes and the reapplication of steps 187 known working version with examination of the changes and the re-application of steps
188 to identify the one causing the problem are 188 to identify the one causing the problem are
189 valid for Poky just as they are for any other system. 189 valid for Poky just as they are for any other system.
190 It's impossible to detail every possible potential failure but here are some general 190 Even though it is impossible to detail every possible potential failure,
191 tips to aid in debugging: 191 here are some general tips to aid in debugging:
192 </para> 192 </para>
193 193
194 <section id='usingpoky-debugging-taskfailures'> 194 <section id='usingpoky-debugging-taskfailures'>