From: Howard Chu <hyc@openldap.org>
Date: Wed, 20 Dec 2006 17:02:18 +0000 (+0000)
Subject: cleanup
X-Git-Tag: OPENLDAP_REL_ENG_2_4_4ALPHA~8^2~329
X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=758f4d81546880e0b36ff2028556ffdc73aa7f0c;p=openldap

cleanup
---

diff --git a/doc/man/man8/slappasswd.8 b/doc/man/man8/slappasswd.8
index 0048f7ed3a..93eb204515 100644
--- a/doc/man/man8/slappasswd.8
+++ b/doc/man/man8/slappasswd.8
@@ -137,13 +137,13 @@ provides 31 characters of salt.
 Omit the trailing newline; useful to pipe the credentials
 into a command.
 .SH LIMITATIONS
-The practice storing hashed passwords in userPassword violates
+The practice of storing hashed passwords in userPassword violates
 Standard Track (RFC 4519) schema specifications and may hinder
 interoperability.  A new attribute type, authPassword, to hold
 hashed passwords has been defined (RFC 3112), but is not yet
 implemented in
 .BR slapd (8).
-.TP
+.LP
 It should also be noted that the behavior of
 .BR crypt (3)
 is platform specific.
@@ -151,7 +151,7 @@ is platform specific.
 Use of hashed passwords does not protect passwords during
 protocol transfer.  TLS or other eavesdropping protections
 should be in\-place before using LDAP simple bind.
-.TP
+.LP
 The hashed password values should be protected as if they
 were clear text passwords.
 .SH "SEE ALSO"