summaryrefslogtreecommitdiff
path: root/Documentation/filesystems/xfs-self-describing-metadata.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/filesystems/xfs-self-describing-metadata.txt')
-rw-r--r--Documentation/filesystems/xfs-self-describing-metadata.txt2
1 files changed, 1 insertions, 1 deletions
diff --git a/Documentation/filesystems/xfs-self-describing-metadata.txt b/Documentation/filesystems/xfs-self-describing-metadata.txt
index 05aa455163e3..68604e67a495 100644
--- a/Documentation/filesystems/xfs-self-describing-metadata.txt
+++ b/Documentation/filesystems/xfs-self-describing-metadata.txt
@@ -110,7 +110,7 @@ owner field in the metadata object, we can immediately do top down validation to
determine the scope of the problem.
Different types of metadata have different owner identifiers. For example,
-directory, attribute and extent tree blocks are all owned by an inode, whilst
+directory, attribute and extent tree blocks are all owned by an inode, while
freespace btree blocks are owned by an allocation group. Hence the size and
contents of the owner field are determined by the type of metadata object we are
looking at. The owner information can also identify misplaced writes (e.g.