diff options
| author | Randy Dunlap <rdunlap@infradead.org> | 2023-07-04 02:20:24 +0300 |
|---|---|---|
| committer | Jonathan Corbet <corbet@lwn.net> | 2023-07-14 22:17:55 +0300 |
| commit | 97e6f1351b13d192fb782003c9322ebceb1fde67 (patch) | |
| tree | 392c038e1aa0f133027792211b91ab1caf1e2dab | |
| parent | c15ec3d1a287698830798111ede1b7ae0bfef7f6 (diff) | |
| download | linux-97e6f1351b13d192fb782003c9322ebceb1fde67.tar.xz | |
Documentation: admin-guide: correct "it's" to possessive "its"
Correct 2 uses of "it's" to the possessive "its" as needed.
Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
Cc: Darrick J. Wong <djwong@kernel.org>
Cc: linux-xfs@vger.kernel.org
Cc: linux-mm@kvack.org
Cc: Jonathan Corbet <corbet@lwn.net>
Reviewed-by: Darrick J. Wong <djwong@kernel.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20230703232024.8069-1-rdunlap@infradead.org
| -rw-r--r-- | Documentation/admin-guide/mm/numa_memory_policy.rst | 2 | ||||
| -rw-r--r-- | Documentation/admin-guide/xfs.rst | 2 |
2 files changed, 2 insertions, 2 deletions
diff --git a/Documentation/admin-guide/mm/numa_memory_policy.rst b/Documentation/admin-guide/mm/numa_memory_policy.rst index 46515ad2337f..eca38fa81e0f 100644 --- a/Documentation/admin-guide/mm/numa_memory_policy.rst +++ b/Documentation/admin-guide/mm/numa_memory_policy.rst @@ -109,7 +109,7 @@ VMA Policy * A task may install a new VMA policy on a sub-range of a previously mmap()ed region. When this happens, Linux splits the existing virtual memory area into 2 or 3 VMAs, each with - it's own policy. + its own policy. * By default, VMA policy applies only to pages allocated after the policy is installed. Any pages already faulted into the diff --git a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst index 3a9c041d7f6c..b67772cf36d6 100644 --- a/Documentation/admin-guide/xfs.rst +++ b/Documentation/admin-guide/xfs.rst @@ -192,7 +192,7 @@ When mounting an XFS filesystem, the following options are accepted. are any integer multiple of a valid ``sunit`` value. Typically the only time these mount options are necessary if - after an underlying RAID device has had it's geometry + after an underlying RAID device has had its geometry modified, such as adding a new disk to a RAID5 lun and reshaping it. |