From 73805e7c1b9ac98db04c4b2e524c5bbb409c8aeb Mon Sep 17 00:00:00 2001
From: ddomingo <ddomingo@redhat.com>
Date: Wed, 5 Nov 2008 16:29:20 +1000
Subject: proofread run 3

---
 .../en-US/CrossInstrumenting.xml                   |  7 +--
 .../en-US/Using_SystemTap.xml                      | 63 +++++++++++-----------
 2 files changed, 35 insertions(+), 35 deletions(-)

(limited to 'doc/SystemTap_Beginners_Guide')

diff --git a/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml b/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml
index 8a772f15..5e29307c 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/CrossInstrumenting.xml
@@ -33,16 +33,13 @@
   <itemizedlist>
     <listitem>
       <para>
-	The debug RPMs for various machines can be installed on a single system:
-	the host machine.
+	The kernel information packages for various machines can be installed on a single <emphasis>host machine</emphasis>.
       </para>
     </listitem>
 
     <listitem>
       <para>
-	Each target machine only needs one RPM to installed to use
-	the generated SystemTap instrumentation module:
-	<filename>systemtap-runtime</filename>.
+	Each <emphasis>target machine</emphasis> only needs one RPM to installed to use the generated SystemTap instrumentation module: <filename>systemtap-runtime</filename>.
       </para>
     </listitem>
   </itemizedlist>
diff --git a/doc/SystemTap_Beginners_Guide/en-US/Using_SystemTap.xml b/doc/SystemTap_Beginners_Guide/en-US/Using_SystemTap.xml
index 447f3d62..1a21dbcb 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/Using_SystemTap.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/Using_SystemTap.xml
@@ -28,14 +28,44 @@
 		<para>
 			SystemTap scripts are run through the command <command>stap</command>. <command>stap</command> can run SystemTap scripts from standard input or from file.
 		</para>
-		
+<!--		
 <important>
 	<title>Important</title>
 <para>Running SystemTap requires root privileges. As such, you need to either log in as root or configure <command>sudo</command> accordingly for specific users who need to run SystemTap (refer to <command>man sudo</command> or <command>man visudo</command> for more information.</para> 
 
 </important>
-		
-		
+		-->
+
+<!--<formalpara>
+	<title>stapdev and stapusr</title>-->
+	<para>Running <command>stap</command> and <command>staprun</command> requires elevated privileges to the system. However, not all users can be granted root access just to run SystemTap. In some cases, for instance, you may want to allow a non-privileged user to run SystemTap instrumentation on his machine.</para>
+<!-- </formalpara> -->
+
+<para>To allow ordinary users to run SystemTap without root access, add them to one of these user groups:</para>
+
+<variablelist>
+	
+<varlistentry>
+	<term>stapdev</term>
+	<listitem>
+<para>
+	Members of this group can use <command>stap</command> to run SystemTap scripts, or <command>staprun</command> to run SystemTap instrumentation modules.
+</para>
+	</listitem>
+</varlistentry>
+
+<varlistentry>
+	<term>stapusr</term>
+	<listitem>
+<para>
+	Members of this group can only run <command>staprun</command> to run SystemTap instrumentation modules. In addition, they can only run those modules from <filename>/lib/modules/<replaceable>kernel_version</replaceable>/systemtap/</filename>. Note that this directory must be owned only by the root user, and must only be writable by the root user.
+</para>
+</listitem>
+</varlistentry>
+</variablelist>		
+
+
+
 		<para> Below is a list of commonly used <command>stap</command> options: </para>
 		
 <variablelist>
@@ -117,33 +147,6 @@ echo "probe timer.s(1) {exit()}" | stap -
 	<para>The <command>stap</command> options <command>-v</command> and <command>-o</command> also work for <command>staprun</command>. For more information about <command>staprun</command>, refer to <command>man staprun</command>.</para>
 </note>	
 
-<formalpara>
-	<title>stapdev and stapusr</title>
-	<para>Running <command>stap</command> and <command>staprun</command> requires elevated privileges to the system. However, not all users can be granted root access just to run SystemTap. In some cases, for instance, you may want to allow a non-privileged user to run SystemTap instrumentation on his machine.</para>
-</formalpara>
-
-<para>To allow ordinary users to run SystemTap without root access, add them to one of these user groups:</para>
-
-<variablelist>
-	
-<varlistentry>
-	<term>stapdev</term>
-	<listitem>
-<para>
-	Members of this group can use <command>stap</command> to run SystemTap scripts, or <command>staprun</command> to run SystemTap instrumentation modules.
-</para>
-	</listitem>
-</varlistentry>
-
-<varlistentry>
-	<term>stapusr</term>
-	<listitem>
-<para>
-	Members of this group can only run <command>staprun</command> to run SystemTap instrumentation modules. In addition, they can only run those modules from <filename>/lib/modules/<replaceable>kernel_version</replaceable>/systemtap/</filename>. Note that this directory must be owned only by the root user, and must only be writable by the root user.
-</para>
-</listitem>
-</varlistentry>
-</variablelist>
 	</section>
 
 </chapter>
-- 
cgit