summaryrefslogtreecommitdiffstats
path: root/Documentation/filesystems/sharedsubtree.txt
diff options
context:
space:
mode:
authorJavi Merino <javi.merino@arm.com>2016-02-25 12:19:56 +0100
committerJonathan Corbet <corbet@lwn.net>2016-03-09 23:33:06 +0100
commitc22d6bef7caca3616720417996cb3e2629430929 (patch)
treea51605e9ffb45a7c1dcaf914c02033f734e20535 /Documentation/filesystems/sharedsubtree.txt
parentDocumentation: Howto: Fixed subtitles style (diff)
downloadlinux-c22d6bef7caca3616720417996cb3e2629430929.tar.xz
linux-c22d6bef7caca3616720417996cb3e2629430929.zip
doc: fix grammar
Some minor typos: - make is unbindable -> make it unbindable - a underlying -> an underlying - different version -> different versions Cc: Jonathan Corbet <corbet@lwn.net> Signed-off-by: Javi Merino <javi.merino@arm.com> Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Diffstat (limited to 'Documentation/filesystems/sharedsubtree.txt')
-rw-r--r--Documentation/filesystems/sharedsubtree.txt8
1 files changed, 4 insertions, 4 deletions
diff --git a/Documentation/filesystems/sharedsubtree.txt b/Documentation/filesystems/sharedsubtree.txt
index e3f4c778eb98..8ccfbd55244b 100644
--- a/Documentation/filesystems/sharedsubtree.txt
+++ b/Documentation/filesystems/sharedsubtree.txt
@@ -123,7 +123,7 @@ replicas continue to be exactly same.
2d) A unbindable mount is a unbindable private mount
- let's say we have a mount at /mnt and we make is unbindable
+ let's say we have a mount at /mnt and we make it unbindable
# mount --make-unbindable /mnt
@@ -197,13 +197,13 @@ replicas continue to be exactly same.
namespaces are made first class objects with user API to
associate/disassociate a namespace with userid, then each user
could have his/her own namespace and tailor it to his/her
- requirements. Offcourse its needs support from PAM.
+ requirements. This needs to be supported in PAM.
D) Versioned files
If the entire mount tree is visible at multiple locations, then
- a underlying versioning file system can return different
- version of the file depending on the path used to access that
+ an underlying versioning file system can return different
+ versions of the file depending on the path used to access that
file.
An example is: