Unionfs: documentation updates

Signed-off-by: Erez Zadok <ezk@cs.sunysb.edu>

diff --git a/Documentation/filesystems/unionfs/concepts.txt b/Documentation/filesystems/unionfs/concepts.txt
index eb74aacbcc5c2a087a821f0fe7dc1590cf425c13..35ddceaed55f58dc0768eb95c8d401e3cc1e1fc5 100644 (file)
--- a/Documentation/filesystems/unionfs/concepts.txt
+++ b/Documentation/filesystems/unionfs/concepts.txt
@@ -104,7 +104,7 @@ longer in sync with its lower counterparts, then we rebuild that object
 similarly to how we do so for branch-management.
 
 While rebuilding Unionfs's objects, we also purge any page mappings and
-truncate inode pages (see fs/Unionfs/dentry.c:purge_inode_data).  This is to
+truncate inode pages (see fs/unionfs/dentry.c:purge_inode_data).  This is to
 ensure that Unionfs will re-get the newer data from the lower branches.  We
 perform this purging only if the Unionfs operation in question is a reading
 operation; if Unionfs is performing a data writing operation (e.g., ->write,