From 4ab3056c2310b0ab4905f3aa82554cbcc455626f Mon Sep 17 00:00:00 2001
From: jinx <jinx@3ecf2c5c-341e-0410-92b4-d18e462d057c>
Date: Fri, 10 Mar 2006 15:08:15 +0000
Subject: [PATCH] essageMinor correcions

git-svn-id: svn://svn.gna.org/svn/sgpemv2/trunk@526 3ecf2c5c-341e-0410-92b4-d18e462d057c
---
 doc/sgpem2uman.texi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/doc/sgpem2uman.texi b/doc/sgpem2uman.texi
index 547ecdb..99d109d 100644
--- a/doc/sgpem2uman.texi
+++ b/doc/sgpem2uman.texi
@@ -484,7 +484,7 @@ Please note how the word ``priority'' here has a general meaning: it indicates e
 can bubble up the sorted ready queue and come before another. So it's up 
 to Policy.sort_queue() to give it a precise meaning.
 
-@sp1
+@sp 1
 @item body of @code{def get_time_slice(self):} line 10 - Returns how long is a time-slice for this policy. 
 A time sliced policy should return a positive integer value, a policy which doesn't use slices should instead 
 return -1. You're encouraged to use a user-configurable parameter via Policy.configure() if the policy is