Few typos in language reference and tutorial

[Miroslav Franc <mfranc at redhat dot com>]

Hi, I was going through language reference and tutorial and found some
typos.  Not sure what is correct procedure here.  Should I file a bug or
is a patch enough?


diff --git a/doc/langref.tex b/doc/langref.tex
index caf9016..d0c0508 100644
--- a/doc/langref.tex
+++ b/doc/langref.tex
@@ -94,7 +94,7 @@ problem. SystemTap was designed to eliminate the need for a developer to
 go through the tedious instrument, recompile, install, and reboot sequence
 normally required to collect this kind of data. To do this, it provides a
 simple command-line interface and scripting language for writing
-instrumenation for both kernel and user space.
+instrumentation for both kernel and user space.
 With SystemTap, developers, system administrators, and users can easily write
 scripts that gather and manipulate system data that is otherwise unavailable
 from standard Linux tools. Users of SystemTap will find it to be a significant
@@ -989,8 +989,8 @@ General syntax:
 
 \begin{vindent}
 \begin{verbatim}
-kernel.function("func[@file]"
-module("modname").function("func[@file]"
+kernel.function("func[@file]")
+module("modname").function("func[@file]")
 \end{verbatim}
 \end{vindent}
 Examples:
diff --git a/doc/tutorial.tex b/doc/tutorial.tex
index a5a4c17..7b4fde5 100644
--- a/doc/tutorial.tex
+++ b/doc/tutorial.tex
@@ -470,7 +470,7 @@ Systemtap allows limited dereferencing of such pointer chains.
 Two functions, \verb+user_string+ and \verb+kernel_string+, can copy
 \verb+char *+ target variables into systemtap strings.
 Figure~\ref{fig:inode-watch} demonstrates one way to monitor a
-particular file (identifed by device number and inode number).
+particular file (identified by device number and inode number).
 The script selects the appropriate variants of \verb+dev_nr+
 and\verb+inode_nr+ based on the kernel version.
 This example also demonstrates passing numeric command-line arguments
@@ -569,7 +569,7 @@ indexed by some tuple of thread numbers, processor ids, names, time,
 and so on.  Systemtap offers associative arrays for this purpose.
 These arrays are implemented as hash tables with a maximum size that
 is fixed at startup.  Because they are too large to be created
-dynamically for inidividual probes handler runs, they must be declared
+dynamically for individual probes handler runs, they must be declared
 as global.  \nomenclature{array}{A global
 \verb+[+$k_1,k_2,\ldots,k_n\verb+]+\rightarrow value$
 associative lookup table, with a string,


-- 
Miroslav Franc, QE, Tool Chain                mfranc@redhat.com

"During smoke testing you are waiting for magic smoke to appear
whereas during sanity testing you are praying for your sanity."