glusterfs: An effort to fix all the spell mistakes and typo

in the entire glusterfs codebase.

This patch fixes many of spell mistakes and typo in the entire
glusterfs codebase and all supported modules.

Change-Id: I83238a41aa08118df3cf4d1d605505dd3cda35a1
BUG: 3809
Signed-off-by: Harshavardhana <fharshav@redhat.com>
Reviewed-on: http://review.gluster.com/731
Tested-by: Gluster Build System <jenkins@build.gluster.com>
Reviewed-by: Amar Tumballi <amar@gluster.com>
Reviewed-by: Vijay Bellur <vijay@gluster.com>

1 files changed, 5 insertions, 5 deletions

diff --git a/rpc/rpc-lib/src/rpcsvc.h b/rpc/rpc-lib/src/rpcsvc.h
index c6f4325443d..ffdc306e600 100644
--- a/rpc/rpc-lib/src/rpcsvc.h
+++ b/rpc/rpc-lib/src/rpcsvc.h
@@ -187,8 +187,8 @@ struct rpcsvc_request {
         uint64_t                lk_owner;
         uint64_t                gfs_id;
 
-        /* Might want to move this to AUTH_UNIX specifix state since this array
-         * is not available for every authenticatino scheme.
+        /* Might want to move this to AUTH_UNIX specific state since this array
+         * is not available for every authentication scheme.
          */
         gid_t                   auxgids[NGRPS];
         int                     auxgidcount;
@@ -217,8 +217,8 @@ struct rpcsvc_request {
         int                     auth_err;
 
         /* There can be cases of RPC requests where the reply needs to
-         * be built from multiple sources. For eg. where even the NFS reply can
-         * contain a payload, as in the NFSv3 read reply. Here the RPC header
+         * be built from multiple sources. E.g. where even the NFS reply
+         * can contain a payload, as in the NFSv3 read reply. Here the RPC header
          * ,NFS header and the read data are brought together separately from
          * different buffers, so we need to stage the buffers temporarily here
          * before all of them get added to the connection's transmission list.
@@ -323,7 +323,7 @@ typedef struct rpcsvc_actor_desc {
          * the XDR scheme, RPC cannot guarantee memory aligned addresses for
          * the resulting message-specific structures. Allowing a specialized
          * handler for letting the RPC program read the data from the network
-         * directly into its alligned buffers.
+         * directly into its aligned buffers.
          */
         rpcsvc_vector_actor     vector_actor;
         rpcsvc_vector_sizer     vector_sizer;