[Patch] Fix a few typos in the tutorial

[Patch] Fix a few typos in the tutorial

[Ondrej Oprala]

[-- Attachment #1: Type: text/plain, Size: 113 bytes --]

Hi,
  these are extremely minor, I just wanted to fix it for the sake of 
completeness.

Best regards,
  Ondrej


[-- Attachment #2: 0001-Fix-a-few-typos-in-the-tutorial.patch --]
[-- Type: text/x-patch, Size: 1400 bytes --]

From b63feba1d26eade23581313edeb9e7dd996efa60 Mon Sep 17 00:00:00 2001
From: Ondrej Oprala <ooprala@redhat.com>
Date: Fri, 7 Aug 2015 14:49:15 +0200
Subject: [PATCH] Fix a few typos in the tutorial

---
 doc/tutorial.tex | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/tutorial.tex b/doc/tutorial.tex
index eefbc05..2339cab 100644
--- a/doc/tutorial.tex
+++ b/doc/tutorial.tex
@@ -240,7 +240,7 @@ tapset library}, but here's a sampling:
 \verb+gettimeofday_s()+ & Number of seconds since epoch. \\
 \verb+get_cycles()+ & Snapshot of hardware cycle counter. \\
 \verb+pp()+ & A string describing the probe point being currently handled. \\
-\verb+ppfunc()+ & If known, the the function name in which this probe was
+\verb+ppfunc()+ & If known, the function name in which this probe was
                   placed. \\
 \verb+$$vars+ & If available, a pretty-printed listing of all local
                 variables in scope. \\
@@ -937,7 +937,7 @@ zsh/process: 5
 \subsection{Embedded C}
 \label{embedded-c}
 
-Sometimes, a tapset needs provide data values from the kernel that
+Sometimes, a tapset needs to provide data values from the kernel that
 cannot be extracted using ordinary target variables (\verb+$var+).  %$
 This may be because the values are in complicated data structures, may
 require lock awareness, or are defined by layers of macros.  Systemtap
-- 
2.4.3