--- ntlm_auth.1-orig	2006-12-21 11:41:10.000000000 -0500
+++ ntlm_auth.1	2006-12-21 11:44:27.000000000 -0500
@@ -88,7 +88,7 @@
 
 This protocol consists of lines in for form: \fBParameter: value\fR and \fBParamter:: Base64\-encode value\fR\&. The presence of a single period \fB\&.\fR indicates that one side has finished supplying data to the other\&. (Which in turn could cause the helper to authenticate the user)\&.
 
-Curently implemented parameters from the external program to the helper are:
+Currently implemented parameters from the external program to the helper are:
 
 .RS
 
@@ -150,16 +150,18 @@
 
 .TP
 Request\-LanMan\-Session\-Key
-Apon sucessful authenticaiton, return the LANMAN session key associated with the login\&.
+Upon sucessful authentication, return the LANMAN session key associated with the login\&.
 
 Example 13. Request\-LanMan\-Session\-Key: Yes
-.RS .Sh "Warning" Implementors should take care to base64 encode any data (such as usernames/passwords) that may contain malicous user data, such as a newline\&. They may also need to decode strings from the helper, which likewise may have been base64 encoded\&. .RE
-
+.RS 
+.Sh Warning: 
+Implementors should take care to base64 encode any data (such
+as usernames/passwords) that may contain malicious user data, such as
+a newline\&. They may also need to decode strings from the helper,
+which likewise may have been base64 encoded\&. 
+.RE
 .RE
-.IP
-
 .RE
-.IP
 
 .TP
 \-\-username=USERNAME