diff options
author | Paolo Ornati <ornati@fastwebnet.it> | 2006-10-03 22:57:56 +0200 |
---|---|---|
committer | Adrian Bunk <bunk@stusta.de> | 2006-10-03 22:57:56 +0200 |
commit | 670e9f34ee3c7e052514c85014d2fdd99b672cdc (patch) | |
tree | 41f82a763ba6d5ca2fcb84d6a05808d095d4d051 /Documentation/filesystems/directory-locking | |
parent | 53cb47268e6b38180d9f253527135e1c69c5d310 (diff) |
Documentation: remove duplicated words
Remove many duplicated words under Documentation/ and do other small
cleanups.
Examples:
"and and" --> "and"
"in in" --> "in"
"the the" --> "the"
"the the" --> "to the"
...
Signed-off-by: Paolo Ornati <ornati@fastwebnet.it>
Signed-off-by: Adrian Bunk <bunk@stusta.de>
Diffstat (limited to 'Documentation/filesystems/directory-locking')
-rw-r--r-- | Documentation/filesystems/directory-locking | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/filesystems/directory-locking b/Documentation/filesystems/directory-locking index 34380d4fbce..d7099a9266f 100644 --- a/Documentation/filesystems/directory-locking +++ b/Documentation/filesystems/directory-locking @@ -82,7 +82,7 @@ own descendent. Moreover, there is exactly one cross-directory rename Consider the object blocking the cross-directory rename. One of its descendents is locked by cross-directory rename (otherwise we -would again have an infinite set of of contended objects). But that +would again have an infinite set of contended objects). But that means that cross-directory rename is taking locks out of order. Due to (2) the order hadn't changed since we had acquired filesystem lock. But locking rules for cross-directory rename guarantee that we do not |