From 5ed6652ae1f8ffd3509f036d35d4cf8dbca5e573 Mon Sep 17 00:00:00 2001
From: Scott Rifenbark <scott.m.rifenbark@intel.com>
Date: Thu, 23 Jun 2011 13:41:03 -0700
Subject: [PATCH] documentation/adt-manual/adt-eclipse.xml: General minor edits
 (From yocto-docs rev: c79d17e29d5690a8df9943836286232cd3aa8893)

Signed-off-by: Scott Rifenbark <scott.m.rifenbark@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
---
 documentation/adt-manual/adt-eclipse.xml | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/documentation/adt-manual/adt-eclipse.xml b/documentation/adt-manual/adt-eclipse.xml
index d64e12270d..4dd90f52fd 100644
--- a/documentation/adt-manual/adt-eclipse.xml
+++ b/documentation/adt-manual/adt-eclipse.xml
@@ -288,7 +288,7 @@
         You can change these settings for a given project by following these steps:
         <orderedlist>
             <listitem><para>Select Project -> Invoke Yocto Tools -> Reconfigure Yocto.  
-            This brings up the project Yocto Settings Dialog.  
+            This brings up the project's Yocto Settings Dialog.  
             Settings are inherited from the default project configuration.  
             The information in this dialogue is identical to that chosen earlier 
             for the Cross Compiler Option (Stand-alone Prebuilt Toolchain or Build System Derived Toolchain), 
@@ -309,7 +309,7 @@
 <title>Building the Project</title>
     <para>
         To build the project, select Project -&gt; Build Project.  
-        You should see the console updated and you can note the cross-compiler you are using.
+        The console should update and you can note the cross-compiler you are using.
     </para>
 </section>
 
@@ -401,10 +401,10 @@
             on your local host machine.  
             The oprofile-server is installed by default in the image.</para></listitem>
             <listitem><para><emphasis>Lttng-ust:</emphasis>  Selecting this tool runs 
-            "usttrace" on the remote target, transfers the output data back to the 
-            local host machine and uses "lttv-gui" to graphically display the output.  
-            The "lttv-gui" must be installed on the local host machine to use this tool.  
-            For information on how to use "lttng" to trace an application, see 
+            <filename>usttrace</filename> on the remote target, transfers the output data back to the 
+            local host machine and uses <filename>lttv-gui</filename> to graphically display the output.  
+            The <filename>lttv-gui</filename> must be installed on the local host machine to use this tool.  
+            For information on how to use <filename>lttng</filename> to trace an application, see 
             <ulink url='http://lttng.org/files/ust/manual/ust.html'></ulink>.</para>
             <para>For "Application" you must supply the absolute path name of the 
             application to be traced by user mode lttng.  
@@ -418,10 +418,10 @@
             new view called "powertop".</para>
             <para>"Time to gather data(sec):" is the time passed in seconds before data 
             is gathered from the remote target for analysis.</para>
-            <para>"show pids in wakeups list:" corresponds to the -p argument 
-            passed to "powertop".</para></listitem>
+            <para>"show pids in wakeups list:" corresponds to the <filename>-p</filename> argument 
+            passed to <filename>powertop</filename>.</para></listitem>
             <listitem><para><emphasis>LatencyTOP and Perf:</emphasis>  "LatencyTOP" 
-            identifies system latency, while "perf" monitors the system's 
+            identifies system latency, while <filename>perf</filename> monitors the system's 
             performance counter registers. 
             Selecting either of these tools causes an RSE terminal view to appear 
             from which you can run the tools.