From 3da34b09f2581093983ca29c2522a500c569a9ca Mon Sep 17 00:00:00 2001
From: William Cohen <wcohen@redhat.com>
Date: Wed, 21 Jan 2009 17:08:34 -0500
Subject: Update copyright date and correct paragraph.

---
 doc/ChangeLog                               |  4 ++++
 doc/SystemTap_Tapset_Reference/tapsets.tmpl | 11 +++++------
 2 files changed, 9 insertions(+), 6 deletions(-)

(limited to 'doc')

diff --git a/doc/ChangeLog b/doc/ChangeLog
index 33ff669b..ef31a5ea 100644
--- a/doc/ChangeLog
+++ b/doc/ChangeLog
@@ -1,3 +1,7 @@
+2009-01-21  William Cohen <wcohen@redhat.com>
+
+	* S_T_R/tapsets.tmpl: Update copyright date and correct paragraph.
+	
 2009-01-12  William Cohen <wcohen@elastic.org>
 	
 	* S_T_R/tapsets.tmpl: Correct author's name.
diff --git a/doc/SystemTap_Tapset_Reference/tapsets.tmpl b/doc/SystemTap_Tapset_Reference/tapsets.tmpl
index ac06e87a..cbbc3b3a 100644
--- a/doc/SystemTap_Tapset_Reference/tapsets.tmpl
+++ b/doc/SystemTap_Tapset_Reference/tapsets.tmpl
@@ -19,7 +19,7 @@
   </authorgroup>
 
   <copyright>
-   <year>2008</year>
+   <year>2008, 2009</year>
    <holder>Red Hat, Inc.</holder>
   </copyright>
 
@@ -92,11 +92,10 @@
       </para>
 
       <para>
-	In some cases, tapsets do not have a <replaceable>return</replaceable> v
-alue. This
-	simply means that the tapset does not extract anything from the kernel. 
-This is common among 
-	asynchronous events such as timers, exit functions, and print functions.
+	In some cases, tapsets do not have a <replaceable>return</replaceable>
+	value. This simply means that the tapset does not extract anything from
+	the kernel.  This is common among asynchronous events such as timers,
+	exit functions, and print functions.
       </para>
 
 <!--
-- 
cgit