diff options
Diffstat (limited to 'include')
| -rw-r--r-- | include/rpc/auth.h | 2 | ||||
| -rw-r--r-- | include/rpc/rpc_msg.h | 2 | ||||
| -rw-r--r-- | include/rpc/xdr.h | 2 | ||||
| -rw-r--r-- | include/rpcsvc/nis.x | 2 |
4 files changed, 4 insertions, 4 deletions
diff --git a/include/rpc/auth.h b/include/rpc/auth.h index 4f23e5e..5cb9abd 100644 --- a/include/rpc/auth.h +++ b/include/rpc/auth.h @@ -40,7 +40,7 @@ * Copyright (C) 1984, Sun Microsystems, Inc. * * The data structures are completely opaque to the client. The client - * is required to pass a AUTH * to routines that create rpc + * is required to pass an AUTH * to routines that create rpc * "sessions". */ diff --git a/include/rpc/rpc_msg.h b/include/rpc/rpc_msg.h index 45fd261..354b341 100644 --- a/include/rpc/rpc_msg.h +++ b/include/rpc/rpc_msg.h @@ -187,7 +187,7 @@ extern bool_t xdr_replymsg(XDR *, struct rpc_msg *); /* - * XDR routine to handle a accepted rpc reply. + * XDR routine to handle an accepted rpc reply. * xdr_accepted_reply(xdrs, rej) * XDR *xdrs; * struct accepted_reply *rej; diff --git a/include/rpc/xdr.h b/include/rpc/xdr.h index 7af99ce..f389bcd 100644 --- a/include/rpc/xdr.h +++ b/include/rpc/xdr.h @@ -233,7 +233,7 @@ xdr_putint32(XDR *xdrs, int32_t *ip) /* * Support struct for discriminated unions. * You create an array of xdrdiscrim structures, terminated with - * a entry with a null procedure pointer. The xdr_union routine gets + * an entry with a null procedure pointer. The xdr_union routine gets * the discriminant value and then searches the array of structures * for a matching value. If a match is found the associated xdr routine * is called to handle that part of the union. If there is diff --git a/include/rpcsvc/nis.x b/include/rpcsvc/nis.x index 748caf6..c1c4851 100644 --- a/include/rpcsvc/nis.x +++ b/include/rpcsvc/nis.x @@ -192,7 +192,7 @@ struct ping_args { /* * These are the type of entries that are stored in the transaction log, * note that modifications will appear as two entries, for names, they have - * a "OLD" entry followed by a "NEW" entry. For entries in tables, there + * an "OLD" entry followed by a "NEW" entry. For entries in tables, there * is a remove followed by an add. It is done this way so that we can read * the log backwards to back out transactions and forwards to propogate * updated. |
