* highlight that getpwent() doesn't suppress duplicate info from multiple

nsswitch.conf sources
* consistently refer to `functions', rather than occasionally referring
  to them as `routines'.

lib/libc/gen/getpwent.3

@@ -1,4 +1,4 @@
-.\"	$NetBSD: getpwent.3,v 1.14 1999/01/16 07:59:39 lukem Exp $
+.\"	$NetBSD: getpwent.3,v 1.15 1999/04/25 13:45:02 lukem Exp $
 .\"
 .\" Copyright (c) 1988, 1991, 1993
 .\"	The Regents of the University of California.  All rights reserved.
@@ -33,7 +33,7 @@
 .\"
 .\"     @(#)getpwent.3	8.2 (Berkeley) 12/11/93
 .\"
-.Dd January 16, 1999
+.Dd April 25, 1999
 .Dt GETPWENT 3
 .Os
 .Sh NAME
@@ -110,7 +110,7 @@ to ``rewind'' to the beginning of the database.
 Additionally, if
 .Fa stayopen
 is non-zero, file descriptors are left open, significantly speeding
-up subsequent accesses for all of the routines.
+up subsequent accesses for all of the functions.
 (This latter functionality is unnecessary for
 .Fn getpwent
 as it doesn't close its file descriptors by default.)
@@ -131,7 +131,7 @@ The
 function
 closes any open files.
 .Pp
-These routines have been written to ``shadow'' the password file, e.g.
+These functions have been written to ``shadow'' the password file, e.g.
 allow only certain programs to have access to the encrypted password.
 If the process which calls them has an effective uid of 0, the encrypted
 password will be returned, otherwise, the password field of the returned
@@ -204,7 +204,7 @@ a pointer to that object. Subsequent calls to
 any of these functions
 will modify the same object.
 .Pp
-The routines
+The functions
 .Fn getpwent ,
 .Fn endpwent ,
 .Fn setpassent ,
@@ -212,6 +212,10 @@ and
 .Fn setpwent
 are fairly useless in a networked environment and should be
 avoided, if possible.
+.Fn getpwent
+makes no attempt to suppress duplicate information if multiple
+sources are specified in
+.Xr nsswitch.conf 5
 .Sh COMPATIBILITY
 The historic function
 .Fn setpwfile