changes as per tech review wcohen, run 1

4 files changed, 28 insertions, 6 deletions

diff --git a/doc/SystemTap_Beginners_Guide/en-US/Errors.xml b/doc/SystemTap_Beginners_Guide/en-US/Errors.xml
index 13adc64f..3dbad229 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/Errors.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/Errors.xml
@@ -28,7 +28,7 @@
       replicate?</remark>
 
 <para>
-      The following invalid SystemTap script is missing the the probe
+      The following invalid SystemTap script is missing the its probe
       handlers:
 </para>
 
diff --git a/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml b/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml
index dbca02fc..d63d7f8c 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/Introduction.xml
@@ -57,9 +57,12 @@
 			** Short summary; when is SystemTap suitable vs other popular monitoring tools (e.g. top, Oprofile, /proc)
 		</remark>
 		
+	<para>SystemTap was originally developed as a working &PROD; version of old Linux probing tools such as <application>dprobes</application> and the Linux Trace Toolkit. SystemTap aims to supplement the existing suite of Linux monitoring tools by providing users with the infrastructure to track kernel activity. In addition, SystemTap combines this capability with two things:</para>		
+		
+<!--		
 		<para>SystemTap was originally developed as a working &PROD; version of old Linux probing tools such as <application>dprobes</application> and the Linux Trace Toolkit. Further, SystemTap can also be considered the Linux answer to <firstterm>Dtrace</firstterm>. Dtrace is a Sun Microsystems "dynamic tracing" framework that assists administrators in monitoring  and troubleshooting kernel and user-space applications in real time.</para>
 	
-	<para>SystemTap aims to supplement the existing suite of Linux monitoring tools by providing users with the infrastructure to track kernel activity. In addition, SystemTap combines this capability with two things:</para>
+	<para>SystemTap aims to supplement the existing suite of Linux monitoring tools by providing users with the infrastructure to track kernel activity. In addition, SystemTap combines this capability with two things:</para>-->
 	
 <itemizedlist>
 	<listitem><para>Flexibility: SystemTap's framework allows users to develop simple scripts for investigating and monitoring a wide variety of kernel functions, system calls, and other events that occur in kernel-space. With this, SystemTap is not soo much a <emphasis>tool</emphasis> as it is a system that allows you to develop your own kernel-specific forensic and monitoring tools.</para></listitem>
diff --git a/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml b/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml
index ca507b43..e0b7c12c 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/Scripts.xml
@@ -44,7 +44,7 @@
 	
   <para>
     SystemTap scripts allow insertion of the instrumentation code without
-    recompilation of the code. and allows more flexibility with regard to
+    recompilation of the code and allows more flexibility with regard to
     handlers. Events serve as the triggers for handlers to run; handlers can be
     specified to record specified data and print it in a certain manner.
   </para>
@@ -66,6 +66,23 @@ probe	<replaceable>event</replaceable> {<replaceable>statements</replaceable>}
     single probe, SystemTap will execute the handler when any of the specified
     events occur.
   </para>
+  
+  <para>
+	Each probe has a corresponding <firstterm>statement block</firstterm>. This statement block is 
+	enclosed in braces (<command>{ }</command>) and contains the handlers to be executed per event. 
+	SystemTap executes these handlers (i.e. "statements") in sequence; special separators or 
+	terminators are generally not necessary between multiple handlers.
+  </para>
+
+<note>
+	<title>Note</title>
+	<para>
+		Statement blocks in SystemTap scripts follow the same syntax and semantics as the C 
+		programming language. A statement block can also nest another statement block, although 
+		for the most part this is used only to organize code in the script for the benefit of the 
+		administrator.
+  	</para>
+</note>	
 
   <para>
     Systemtap allow you to write functions to factor out code to be used by a
@@ -314,7 +331,7 @@ probe timer.s(4)
   </section>
 
   <section id="systemtapscript-handler">
-    <title>Systemtap Handler/Boddy</title>
+    <title>Systemtap Handler/Body</title>
 
     <para> Consider the following sample script: </para>
 
@@ -462,13 +479,14 @@ hald(2360) open
 		<para>The number of seconds since UNIX epoch (January 1, 1970).</para>
 	</listitem>	
 </varlistentry>
-
+<!--
 <varlistentry>
 	<term>get_cycles()</term>
 	<listitem>
 		<para>A snapshot of the hardware cycle counter.</para>
 	</listitem>	
 </varlistentry>
+-->
 
 <varlistentry>
 	<term>pp()</term>
diff --git a/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml b/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml
index 506fea43..2cdfd58f 100644
--- a/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml
+++ b/doc/SystemTap_Beginners_Guide/en-US/Understanding_How_SystemTap_Works.xml
@@ -58,7 +58,8 @@
 	<para>
 	  First, SystemTap checks the script against the existing tapset library
 	  (normally in <filename>/usr/share/systemtap/tapset/</filename> for any
-	  tapsets used.
+	  tapsets used. SystemTap will then substitute any located tapsets with their
+	  corresponding definitions in the tapset library.
 	</para>
       </step>