summaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/vfs.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/filesystems/vfs.txt')
-rw-r--r--Documentation/filesystems/vfs.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/filesystems/vfs.txt b/Documentation/filesystems/vfs.txt
index 0644c2e2f..7f75f4770 100644
--- a/Documentation/filesystems/vfs.txt
+++ b/Documentation/filesystems/vfs.txt
@@ -5,7 +5,7 @@ A Brief Overview of the Virtual File System
Noone else seems to be writing this, so here's a quick description of what
I've learned while writing lofs...
-The VFS relatively simple, but it is nice not to have to browse through
+The VFS is relatively simple, but it is nice not to have to browse through
pages of code to determine what is expected when writing a filesystem.
Hopefully this helps anyone attempting such a feat, as well as clearing up
a few important points/dependencies.
@@ -133,9 +133,9 @@ struct inode_operations
int (*follow_link) (struct inode *,struct inode *,int,int,struct inode **);
[optional]
- The follow_link function is only nescessary if a filesystem uses a really
+ The follow_link function is only necessary if a filesystem uses a really
twisted form of symbolic links - namely if the symbolic link comes from a
- foriegn filesystem that makes no sense....
+ foreign filesystem that makes no sense....
I threw this one out - too much redundant code!
int (*readpage) (struct inode *, struct page *); [optional]