getgrent_r.3, gethostbyname.3, getmntent.3, getnetent_r.3, getprotoent_r.3, getpwent_r.3, getrpcent_r.3, getservent_r.3, getspnam.3: Global fix: s/non-reentrant/nonrentrant/

The tendency in English, as prescribed in style guides like
Chicago MoS, is towards removing hyphens after prefixes
like "non-" etc.

Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>

man3/getgrent_r.3

@@ -76,7 +76,7 @@ struct group {
 .fi
 .in
 .sp
-The non-reentrant functions return a pointer to static storage,
+The nonreentrant functions return a pointer to static storage,
 where this static storage contains further pointers to group
 name, password and members.
 The reentrant functions described here return all of that in

man3/gethostbyname.3

@@ -397,7 +397,7 @@ or if no entry is found
 .I result
 will be NULL.
 The functions return 0 on success and a nonzero error number on failure.
-In addition to the errors returned by the non-reentrant
+In addition to the errors returned by the nonreentrant
 versions of these functions, if
 .I buf
 is too small, the functions will return

man3/getmntent.3

@@ -173,7 +173,7 @@ a match is found and NULL otherwise.
 /etc/mtab           mounted file system description file
 .fi
 .SH "CONFORMING TO"
-The non-reentrant functions are from SunOS 4.1.3.
+The nonreentrant functions are from SunOS 4.1.3.
 A routine
 .BR getmntent_r ()
 was introduced in HP-UX 10, but it returns an int.

man3/getnetent_r.3

@@ -71,7 +71,7 @@ They differ in the way that the
 structure is returned,
 and in the function calling signature and return value.
 This manual page describes just the differences from
-the non-reentrant functions.
+the nonreentrant functions.
 
 Instead of returning a pointer to a statically allocated
 .I netent
@@ -84,7 +84,7 @@ The
 array is used to store the string fields pointed to by the returned
 .I netent
 structure.
-(The non-reentrant functions allocate these strings in static storage.)
+(The nonreentrant functions allocate these strings in static storage.)
 The size of this array is specified in
 .IR buflen .
 If
@@ -94,7 +94,7 @@ is too small, the call fails with the error
 and the caller must try again with a larger buffer.
 (A buffer of length 1024 bytes should be sufficient for most applications.)
 .\" I can find no information on the required/recommended buffer size;
-.\" the non-reentrant functions use a 1024 byte buffer -- mtk.
+.\" the nonreentrant functions use a 1024 byte buffer -- mtk.
 
 If the function call successfully obtains a network record, then
 .I *result
@@ -108,9 +108,9 @@ The buffer pointed to by
 .I h_errnop
 is used to return the value that would be stored in the global variable
 .I h_errno
-by the non-reentrant versions of these functions.
+by the nonreentrant versions of these functions.
 .\" getnetent.3 doesn't document any use of h_errno, but nevertheless
-.\" the non-reentrant functions no seem to set h_errno.
+.\" the nonreentrant functions no seem to set h_errno.
 .SH "RETURN VALUE"
 On success, these functions return 0.
 On error, a positive error number is returned.

man3/getprotoent_r.3

@@ -68,7 +68,7 @@ They differ in the way that the
 structure is returned,
 and in the function calling signature and return value.
 This manual page describes just the differences from
-the non-reentrant functions.
+the nonreentrant functions.
 
 Instead of returning a pointer to a statically allocated
 .I protoent
@@ -81,7 +81,7 @@ The
 array is used to store the string fields pointed to by the returned
 .I protoent
 structure.
-(The non-reentrant functions allocate these strings in static storage.)
+(The nonreentrant functions allocate these strings in static storage.)
 The size of this array is specified in
 .IR buflen .
 If
@@ -91,7 +91,7 @@ is too small, the call fails with the error
 and the caller must try again with a larger buffer.
 (A buffer of length 1024 bytes should be sufficient for most applications.)
 .\" I can find no information on the required/recommended buffer size;
-.\" the non-reentrant functions use a 1024 byte buffer.
+.\" the nonreentrant functions use a 1024 byte buffer.
 .\" The 1024 byte value is also what the Solaris man page suggests. -- mtk
 
 If the function call successfully obtains a protocol record, then

man3/getpwent_r.3

@@ -78,7 +78,7 @@ struct passwd {
 .fi
 .in
 .sp
-The non-reentrant functions return a pointer to static storage,
+The nonreentrant functions return a pointer to static storage,
 where this static storage contains further pointers to user
 name, password, gecos field, home directory and shell.
 The reentrant functions described here return all of that in

man3/getrpcent_r.3

@@ -68,7 +68,7 @@ They differ in the way that the
 structure is returned,
 and in the function calling signature and return value.
 This manual page describes just the differences from
-the non-reentrant functions.
+the nonreentrant functions.
 
 Instead of returning a pointer to a statically allocated
 .I rpcent
@@ -81,7 +81,7 @@ The
 array is used to store the string fields pointed to by the returned
 .I rpcent
 structure.
-(The non-reentrant functions allocate these strings in static storage.)
+(The nonreentrant functions allocate these strings in static storage.)
 The size of this array is specified in
 .IR buflen .
 If
@@ -91,7 +91,7 @@ is too small, the call fails with the error
 and the caller must try again with a larger buffer.
 (A buffer of length 1024 bytes should be sufficient for most applications.)
 .\" I can find no information on the required/recommended buffer size;
-.\" the non-reentrant functions use a 1024 byte buffer -- mtk.
+.\" the nonreentrant functions use a 1024 byte buffer -- mtk.
 
 If the function call successfully obtains an RPC record, then
 .I *result

man3/getservent_r.3

@@ -68,7 +68,7 @@ They differ in the way that the
 structure is returned,
 and in the function calling signature and return value.
 This manual page describes just the differences from
-the non-reentrant functions.
+the nonreentrant functions.
 
 Instead of returning a pointer to a statically allocated
 .I servent
@@ -81,7 +81,7 @@ The
 array is used to store the string fields pointed to by the returned
 .I servent
 structure.
-(The non-reentrant functions allocate these strings in static storage.)
+(The nonreentrant functions allocate these strings in static storage.)
 The size of this array is specified in
 .IR buflen .
 If
@@ -91,7 +91,7 @@ is too small, the call fails with the error
 and the caller must try again with a larger buffer.
 (A buffer of length 1024 bytes should be sufficient for most applications.)
 .\" I can find no information on the required/recommended buffer size;
-.\" the non-reentrant functions use a 1024 byte buffer -- mtk.
+.\" the nonreentrant functions use a 1024 byte buffer -- mtk.
 
 If the function call successfully obtains a service record, then
 .I *result

man3/getspnam.3

@@ -180,7 +180,7 @@ The functions
 .BR fgetspent_r (),
 and
 .BR sgetspent_r ()
-are similarly analogous to their non-reentrant counterparts.
+are similarly analogous to their nonreentrant counterparts.
 .LP
 Some non-glibc systems also have functions with these names,
 often with different prototypes.
@@ -213,7 +213,7 @@ are available or if an error occurs during processing.
 The functions which have \fIint\fP as the return value return 0 for
 success and \-1 for failure.
 .LP
-For the non-reentrant functions, the return value may point to static area,
+For the nonreentrant functions, the return value may point to static area,
 and may be overwritten by subsequent calls to these functions.
 .LP
 The reentrant functions return zero on success.