dev-manual: Edits to "Profiling with OProfile" section.

(From yocto-docs rev: 4530c0580667e54fdcc84aa4eb2d5e73ab23fca6)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 3 insertions, 2 deletions

diff --git a/documentation/dev-manual/dev-manual-common-tasks.xml b/documentation/dev-manual/dev-manual-common-tasks.xml
index f39b5b1f39..b62dee12f4 100644
--- a/documentation/dev-manual/dev-manual-common-tasks.xml
+++ b/documentation/dev-manual/dev-manual-common-tasks.xml
@@ -4253,7 +4253,7 @@
         <para>
             <ulink url="http://oprofile.sourceforge.net/">OProfile</ulink> is a
             statistical profiler well suited for finding performance
-            bottlenecks in both userspace software and in the kernel.
+            bottlenecks in both user-space software and in the kernel.
             This profiler provides answers to questions like "Which functions does my application spend
             the most time in when doing X?"
             Because the OpenEmbedded build system is well integrated with OProfile, it makes profiling
@@ -4293,7 +4293,8 @@
             <filename><ulink url='&YOCTO_DOCS_REF_URL;#var-DEBUG_BUILD'>DEBUG_BUILD</ulink></filename>
             variable to "1" in the <filename>local.conf</filename> configuration file.
             If you use the <filename>DEBUG_BUILD</filename> variable,
-            you will also add extra debug information that can make the debug packages large.
+            you also add extra debugging information that can make the debug 
+            packages large.
         </para>
 
         <section id="platdev-oprofile-target">