From ecbb398cd9b6715058173b1085825e56873aaace Mon Sep 17 00:00:00 2001
From: Dan Olson <theoddone33@users.sourceforge.net>
Date: Fri, 14 Apr 2000 14:37:25 +0000
Subject: [PATCH] fourth draft

---
 speed_cheat.php | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/speed_cheat.php b/speed_cheat.php
index 26f19d8..790adfa 100644
--- a/speed_cheat.php
+++ b/speed_cheat.php
@@ -17,7 +17,7 @@
 				$focused = "none";					// name of focused icon
 				include( "parts/topmain.php" );	// Display content top table
 			?>
-			<h3>How does it work?</h3>
+			<h4>How does it work?</h4>
 			<P>
 			The speed cheat works by the client lying to the server
 			about how much time has passed since the last packet
@@ -26,7 +26,7 @@
 			times from all the movement packets received from a 
 			specific client. If the client says that more then 30 
 			seconds have passed in 30 seconds, a red flag is raised.
-			<h3>Are there any problems with this?</h3>
+			<h4>Are there any problems with this?</h4>
 			<p>
 			Sadly the Windows QuakeWorld clients before 2.33 had a 
 			bug in keeping track of time. The longer Windows is up,
@@ -38,7 +38,7 @@
 			This and several other factors can cause the time 
 			reported by the client to be over the time the server
 			expects.  Lag and packet loss are some of these factors.
-			<h3>Well, what can I do?</h3>
+			<h4>Well, what can I do?</h4>
 			<p>
 			Recongnizing these concerns, we decided to make the
 			cheat detection adjustible for server admins. Here are
@@ -61,7 +61,7 @@
 			<em>sv_timekick_interval</em>: This cvar controls how 
 			often, in seconds, the time tally is counted. Lowering 
 			this value increases the chance of false positives, but
-			helps to minimize the amount of damage a speedcheating
+			helps to minimize the amount of damage a speed-cheating
 			player can cause. Default is 30 seconds.	
 	</TD>
 		<?php