From 6167c66758de454284560474f3b4a893d8a69965 Mon Sep 17 00:00:00 2001 From: Amar Tumballi Date: Fri, 18 Mar 2011 00:41:08 +0000 Subject: spelling errors fixed across the code base recieve -> receive maintainence -> maintenance verison -> version commited -> committed Signed-off-by: Amar Tumballi Signed-off-by: Vijay Bellur BUG: 2262 (Spelling errors in source) URL: http://bugs.gluster.com/cgi-bin/bugzilla3/show_bug.cgi?id=2262 --- doc/hacker-guide/write-behind.txt | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'doc') diff --git a/doc/hacker-guide/write-behind.txt b/doc/hacker-guide/write-behind.txt index 498e95480ae..a6e9a8890e4 100644 --- a/doc/hacker-guide/write-behind.txt +++ b/doc/hacker-guide/write-behind.txt @@ -9,7 +9,7 @@ basic working 2. VFS ==> FUSE ==> /dev/fuse. 3. fuse-bridge initiates a glusterfs writev() call. 4. writev() is STACK_WIND()ed upto client-protocol or storage translator. - 5. client-protocol, on recieving reply from server, starts STACK_UNWIND() towards the fuse-bridge. + 5. client-protocol, on receiving reply from server, starts STACK_UNWIND() towards the fuse-bridge. on a translator tree with write-behind, control flow is like this: @@ -30,7 +30,7 @@ windowing write_behind: if set, indicates that write-behind has done STACK_UNWIND() towards fuse-bridge. - got_reply: if set, indicates that write-behind has recieved reply from child translator for a writev() STACK_WIND(). a request will be destroyed by write-behind only if this flag is set. + got_reply: if set, indicates that write-behind has received reply from child translator for a writev() STACK_WIND(). a request will be destroyed by write-behind only if this flag is set. currently pending write requests = aggregate size of requests with write_behind = 1 and got_reply = 0. -- cgit