Subject: [nfsv4] NFSv4.1 wordsmithing: repeated words

From: Mike Eisler <[email-masked]>
Date: Sun, 17 Feb 2008 21:18:46 -0800 (PST)

I wrote a script that hunts for repeated words in the NFSv4.1 spec,
and now plan to make the pending changes captured in the
attached diff.

Index: dictionary.txt
===================================================================
RCS file: /cvs/stdk/NFSv41/dictionary.txt,v
retrieving revision 1.27
diff -u -w -b -r1.27 dictionary.txt
--- dictionary.txt	1 Feb 2008 22:47:38 -0000	1.27
+++ dictionary.txt	18 Feb 2008 05:14:15 -0000
@@ -199,7 +199,6 @@
 COMPOUND4res
 COMPOUND4res.xml
 COMPOUNDs
-CONNN
 CREATE4args
 CREATE4res
 CREATE4resok
Index: nfsv41_middle_file_layout.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_file_layout.xml,v
retrieving revision 1.44
diff -u -w -b -r1.44 nfsv41_middle_file_layout.xml
--- nfsv41_middle_file_layout.xml	17 Feb 2008 00:11:34 -0000	1.44
+++ nfsv41_middle_file_layout.xml	18 Feb 2008 05:14:16 -0000
@@ -154,7 +154,7 @@
    in data server filehandles,
    when the metadata server identity or location
    changes, the data server filehandles it gave out must become
-   become invalid (stale), and so the metadata server must first
+   invalid (stale), and so the metadata server must first
    recall the layouts.
    Invalidating a data server filehandle does not render
    the NFS client's data cache invalid. The client's cache should
@@ -876,7 +876,7 @@
  </t>
  <t>
    If nfl_util & NFL4_UFLG_DENSE is one, this means that
-   that dense packing is being used and the data server files have no holes.
+   dense packing is being used and the data server files have no holes.
    Dense packing might be selected because the data server does not
    (efficiently) support holey files, or because the data server
    cannot recognize read-ahead unless there are no holes.
Index: nfsv41_middle_fileattributes.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_fileattributes.xml,v
retrieving revision 1.41
diff -u -w -b -r1.41 nfsv41_middle_fileattributes.xml
--- nfsv41_middle_fileattributes.xml	31 Jan 2008 17:15:06 -0000	1.41
+++ nfsv41_middle_fileattributes.xml	18 Feb 2008 05:14:16 -0000
@@ -125,7 +125,7 @@
       returned by OPEN.
     </t>
     <t>
-      Named attributes and the named attribute directory may have have 
+      Named attributes and the named attribute directory may have 
       their own (non-named) attributes.  Each of objects must have all 
       of the REQUIRED attributes and may have additional RECOMMENDED 
       attributes.  However, the set of attributes for named attributes 
Index: nfsv41_middle_multi_server_ns.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_multi_server_ns.xml,v
retrieving revision 1.34
diff -u -w -b -r1.34 nfsv41_middle_multi_server_ns.xml
--- nfsv41_middle_multi_server_ns.xml	16 Feb 2008 14:30:25 -0000	1.34
+++ nfsv41_middle_multi_server_ns.xml	18 Feb 2008 05:14:17 -0000
@@ -785,7 +785,7 @@
             addresses connect to the same server (as indicated by the
             two addresses sharing the same the so_major_id value 
             and subsequently confirmed as described in 
-            in <xref target="Trunking" />) justifies
+            <xref target="Trunking" />) justifies
             simultaneous use and there is no fs_locations_info
             attribute information contradicting that.
           </t>
Index: nfsv41_middle_op_cb_sequence.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_op_cb_sequence.xml,v
retrieving revision 1.21
diff -u -w -b -r1.21 nfsv41_middle_op_cb_sequence.xml
--- nfsv41_middle_op_cb_sequence.xml	8 Nov 2007 04:15:21 -0000	1.21
+++ nfsv41_middle_op_cb_sequence.xml	18 Feb 2008 05:14:17 -0000
@@ -45,7 +45,7 @@
     </t>
     <t>
       The value of csa_sequenceid argument relative to
-      to the cached sequence id on the slot falls into one
+      the cached sequence id on the slot falls into one
       of three cases.
       <list style="symbols">
       <t>
Index: nfsv41_middle_op_create_session.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_op_create_session.xml,v
retrieving revision 1.43
diff -u -w -b -r1.43 nfsv41_middle_op_create_session.xml
--- nfsv41_middle_op_create_session.xml	16 Feb 2008 14:30:25 -0000	1.43
+++ nfsv41_middle_op_create_session.xml	18 Feb 2008 05:14:17 -0000
@@ -61,7 +61,7 @@
          sequence number. See
           <xref target="OP_CREATE_SESSION_IMPLEMENTATION" />.
          The corresponding result is csr_sequence, which MUST be equal to
-         to csa_sequence.
+         csa_sequence.
         </t>
       </list>
       </t>
@@ -277,7 +277,7 @@
 	    <vspace blankLines='2' />
  
           The RPCSEC_GSS context for the backchannel is specified via
-          a pair of values of of data type
+          a pair of values of data type
           gsshandle4_t. The data type gsshandle4_t represents an
           RPCSEC_GSS handle, and is
           precisely the same as the data type of the "handle" field of
Index: nfsv41_middle_op_lock.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_op_lock.xml,v
retrieving revision 1.13
diff -u -w -b -r1.13 nfsv41_middle_op_lock.xml
--- nfsv41_middle_op_lock.xml	17 Dec 2007 22:17:39 -0000	1.13
+++ nfsv41_middle_op_lock.xml	18 Feb 2008 05:14:17 -0000
@@ -53,7 +53,7 @@
       In the case where no such state has been established, or the client
       does not have the stateid available, the argument contains the
       stateid of the open file with which this lock is to be associated,
-      together with the lock_owner which which the lock is to be associated.
+      together with the lock_owner which the lock is to be associated.
       The open_to_lock_owner case covers the very first lock done by a
       lock_owner for a given open file and offers a method to use the 
       established state of the open_stateid to transition to the use of 
Index: nfsv41_middle_op_sequence.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_op_sequence.xml,v
retrieving revision 1.35
diff -u -w -b -r1.35 nfsv41_middle_op_sequence.xml
--- nfsv41_middle_op_sequence.xml	16 Feb 2008 14:30:25 -0000	1.35
+++ nfsv41_middle_op_sequence.xml	18 Feb 2008 05:14:18 -0000
@@ -96,7 +96,7 @@
           until at least one backchannel is
           available on any session associated with the client ID.
           If the client fails to re-establish a 
-          a backchannel for the client ID, it is subject to
+          backchannel for the client ID, it is subject to
           having recallable state revoked.
         </t>
         <t hangText="SEQ4_STATUS_CB_PATH_DOWN_SESSION"><vspace />
@@ -120,7 +120,7 @@
           session until a backchannel on the session
           the path is available.
           If the client fails to re-establish a 
-          a backchannel for the session, it is subject to
+          backchannel for the session, it is subject to
           having recallable state revoked.
 
         </t>
@@ -228,7 +228,7 @@
     </t>
     <t>
       The value of sa_sequenceid argument relative to
-      to the cached sequence id on the slot falls into one
+      the cached sequence id on the slot falls into one
       of three cases.
       <list style="symbols">
       <t>
Index: nfsv41_middle_pnfs.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_pnfs.xml,v
retrieving revision 1.72
diff -u -w -b -r1.72 nfsv41_middle_pnfs.xml
--- nfsv41_middle_pnfs.xml	16 Feb 2008 14:35:40 -0000	1.72
+++ nfsv41_middle_pnfs.xml	18 Feb 2008 05:14:18 -0000
@@ -1121,7 +1121,7 @@
   view.  The metadata server has sent a CB_LAYOUTRECALL and receives
   an overlapping LAYOUTGET for the same file before the
   LAYOUTRETURN(s) that respond to the CB_LAYOUTRECALL. There are
-  are three cases:
+  three cases:
 
 <list style="numbers">
 <t>
Index: nfsv41_middle_state_mgmt.xml
===================================================================
RCS file: /cvs/stdk/NFSv41/nfsv41_middle_state_mgmt.xml,v
retrieving revision 1.26
diff -u -w -b -r1.26 nfsv41_middle_state_mgmt.xml
--- nfsv41_middle_state_mgmt.xml	16 Feb 2008 14:30:25 -0000	1.26
+++ nfsv41_middle_state_mgmt.xml	18 Feb 2008 05:14:18 -0000
@@ -405,7 +405,7 @@
         </t>
         <t>
           With this information, an incoming stateid can be validated and 
-          and the appropriate error returned when necessary.  Special and
+          the appropriate error returned when necessary.  Special and
           non-special stateids are handled separately. (See
           <xref target='special_stateid' /> for a discussion of special 
           stateids). 
@@ -635,7 +635,7 @@
 
     </t>
     <t>
-      A client ID's lease can expire when it has been been
+      A client ID's lease can expire when it has been
       at least the lease interval (lease_time) since the
       last lease-renewing SEQUENCE operation was sent
       on any of the client ID's sessions and there must
_______________________________________________
nfsv4 mailing list
[email-masked]
http://www.ietf.org/mailman/listinfo/nfsv4