From: Bingwu Zhang <xtex@aosc.io>

This fixes two small misspells in the filesystems documentation.

Signed-off-by: Bingwu Zhang <xtex@aosc.io>
---
I found these typos when learning about OverlayFS recently.
---
 Documentation/filesystems/iomap/operations.rst | 2 +-
 Documentation/filesystems/overlayfs.rst        | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/Documentation/filesystems/iomap/operations.rst b/Documentation/filesystems/iomap/operations.rst
index ef082e5a4e0c..2c7f5df9d8b0 100644
--- a/Documentation/filesystems/iomap/operations.rst
+++ b/Documentation/filesystems/iomap/operations.rst
@@ -104,7 +104,7 @@ iomap calls these functions:
 
     For the pagecache, races can happen if writeback doesn't take
     ``i_rwsem`` or ``invalidate_lock`` and updates mapping information.
-    Races can also happen if the filesytem allows concurrent writes.
+    Races can also happen if the filesystem allows concurrent writes.
     For such files, the mapping *must* be revalidated after the folio
     lock has been taken so that iomap can manage the folio correctly.
 
diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst
index 4c8387e1c880..d2a277e3976e 100644
--- a/Documentation/filesystems/overlayfs.rst
+++ b/Documentation/filesystems/overlayfs.rst
@@ -156,7 +156,7 @@ A directory is made opaque by setting the xattr "trusted.overlay.opaque"
 to "y".  Where the upper filesystem contains an opaque directory, any
 directory in the lower filesystem with the same name is ignored.
 
-An opaque directory should not conntain any whiteouts, because they do not
+An opaque directory should not contain any whiteouts, because they do not
 serve any purpose.  A merge directory containing regular files with the xattr
 "trusted.overlay.whiteout", should be additionally marked by setting the xattr
 "trusted.overlay.opaque" to "x" on the merge directory itself.

base-commit: 7503345ac5f5e82fd9a36d6e6b447c016376403a
-- 
2.47.1

Bingwu Zhang <xtex@envs.net> writes:

> From: Bingwu Zhang <xtex@aosc.io>
>
> This fixes two small misspells in the filesystems documentation.
>
> Signed-off-by: Bingwu Zhang <xtex@aosc.io>
> ---
> I found these typos when learning about OverlayFS recently.
> ---
>  Documentation/filesystems/iomap/operations.rst | 2 +-
>  Documentation/filesystems/overlayfs.rst        | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)

Applied, thanks.  Welcome to the kernel community!

jon

On Sun, Dec 08, 2024 at 11:54:47AM +0800, Bingwu Zhang wrote:
> From: Bingwu Zhang <xtex@aosc.io>
> 
> This fixes two small misspells in the filesystems documentation.

There's a couple of similar ones if you want to submit some bonus
patches:

$ git grep sytem
Documentation/devicetree/bindings/sound/amlogic,axg-sound-card.yaml:      Base PLL clocks of audio susbsytem, used to configure base clock
Documentation/devicetree/bindings/sound/amlogic,gx-sound-card.yaml:      Base PLL clocks of audio susbsytem, used to configure base clock
Documentation/filesystems/iomap/operations.rst:    Races can also happen if the filesytem allows concurrent writes.
drivers/gpu/drm/xe/xe_bo.c: * On successful completion, the object memory will be moved to sytem memory.
fs/freevxfs/vxfs_super.c: * @fc:                        filesytem context
fs/ocfs2/sysfile.c:                      * return NULL here so that ocfs2_get_sytem_file_inodes
scripts/spelling.txt:sytem||system

On Sun, Dec 08, 2024 at 11:54:47AM +0800, Bingwu Zhang wrote:
> From: Bingwu Zhang <xtex@aosc.io>
> 
> This fixes two small misspells in the filesystems documentation.
> 
> Signed-off-by: Bingwu Zhang <xtex@aosc.io>

Yep, typoes happun, thanks for the patch.
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
> I found these typos when learning about OverlayFS recently.
> ---
>  Documentation/filesystems/iomap/operations.rst | 2 +-
>  Documentation/filesystems/overlayfs.rst        | 2 +-
>  2 files changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/Documentation/filesystems/iomap/operations.rst b/Documentation/filesystems/iomap/operations.rst
> index ef082e5a4e0c..2c7f5df9d8b0 100644
> --- a/Documentation/filesystems/iomap/operations.rst
> +++ b/Documentation/filesystems/iomap/operations.rst
> @@ -104,7 +104,7 @@ iomap calls these functions:
>  
>      For the pagecache, races can happen if writeback doesn't take
>      ``i_rwsem`` or ``invalidate_lock`` and updates mapping information.
> -    Races can also happen if the filesytem allows concurrent writes.
> +    Races can also happen if the filesystem allows concurrent writes.
>      For such files, the mapping *must* be revalidated after the folio
>      lock has been taken so that iomap can manage the folio correctly.
>  
> diff --git a/Documentation/filesystems/overlayfs.rst b/Documentation/filesystems/overlayfs.rst
> index 4c8387e1c880..d2a277e3976e 100644
> --- a/Documentation/filesystems/overlayfs.rst
> +++ b/Documentation/filesystems/overlayfs.rst
> @@ -156,7 +156,7 @@ A directory is made opaque by setting the xattr "trusted.overlay.opaque"
>  to "y".  Where the upper filesystem contains an opaque directory, any
>  directory in the lower filesystem with the same name is ignored.
>  
> -An opaque directory should not conntain any whiteouts, because they do not
> +An opaque directory should not contain any whiteouts, because they do not
>  serve any purpose.  A merge directory containing regular files with the xattr
>  "trusted.overlay.whiteout", should be additionally marked by setting the xattr
>  "trusted.overlay.opaque" to "x" on the merge directory itself.
> 
> base-commit: 7503345ac5f5e82fd9a36d6e6b447c016376403a
> -- 
> 2.47.1
>