On Fri, Nov 18, 2022 at 03:23:17PM -0800, Randy Dunlap wrote: > Correct 2 uses of "it's" to the possessive "its" as needed. > > Signed-off-by: Randy Dunlap <rdunlap@xxxxxxxxxxxxx> > Cc: Darrick J. Wong <djwong@xxxxxxxxxx> > Cc: linux-xfs@xxxxxxxxxxxxxxx > Cc: linux-mm@xxxxxxxxx > Cc: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx> > Cc: Jonathan Corbet <corbet@xxxxxxx> > --- > Documentation/admin-guide/mm/numa_memory_policy.rst | 2 +- > Documentation/admin-guide/xfs.rst | 2 +- Reviewed-by: Darrick J. Wong <djwong@xxxxxxxxxx> --D > 2 files changed, 2 insertions(+), 2 deletions(-) > > diff -- a/Documentation/admin-guide/mm/numa_memory_policy.rst b/Documentation/admin-guide/mm/numa_memory_policy.rst > --- a/Documentation/admin-guide/mm/numa_memory_policy.rst > +++ b/Documentation/admin-guide/mm/numa_memory_policy.rst > @@ -111,7 +111,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 -- a/Documentation/admin-guide/xfs.rst b/Documentation/admin-guide/xfs.rst > --- a/Documentation/admin-guide/xfs.rst > +++ b/Documentation/admin-guide/xfs.rst > @@ -192,7 +192,7 @@ When mounting an XFS filesystem, the fol > 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. >