Fix minor spelling and grammatical issues in the ext4 atomic_writes
documentation.

Signed-off-by: Mallikarjun Thammanavar <mallikarjunst09@gmail.com>
---
 Documentation/filesystems/ext4/atomic_writes.rst | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/Documentation/filesystems/ext4/atomic_writes.rst b/Documentation/filesystems/ext4/atomic_writes.rst
index f65767df3620..b614b5ffe76b 100644
--- a/Documentation/filesystems/ext4/atomic_writes.rst
+++ b/Documentation/filesystems/ext4/atomic_writes.rst
@@ -14,7 +14,7 @@ I/O) on regular files with extents, provided the underlying storage device
 supports hardware atomic writes. This is supported in the following two ways:
 
 1. **Single-fsblock Atomic Writes**:
-   EXT4's supports atomic write operations with a single filesystem block since
+   EXT4 supports atomic write operations with a single filesystem block since
    v6.13. In this the atomic write unit minimum and maximum sizes are both set
    to filesystem blocksize.
    e.g. doing atomic write of 16KB with 16KB filesystem blocksize on 64KB
@@ -50,7 +50,7 @@ Multi-fsblock Implementation Details
 
 The bigalloc feature changes ext4 to allocate in units of multiple filesystem
 blocks, also known as clusters. With bigalloc each bit within block bitmap
-represents cluster (power of 2 number of blocks) rather than individual
+represents a cluster (power of 2 number of blocks) rather than individual
 filesystem blocks.
 EXT4 supports multi-fsblock atomic writes with bigalloc, subject to the
 following constraints. The minimum atomic write size is the larger of the fs
@@ -189,7 +189,7 @@ The write must be aligned to the filesystem's block size and not exceed the
 filesystem's maximum atomic write unit size.
 See ``generic_atomic_write_valid()`` for more details.
 
-``statx()`` system call with ``STATX_WRITE_ATOMIC`` flag can provides following
+``statx()`` system call with ``STATX_WRITE_ATOMIC`` flag can provide following
 details:
 
  * ``stx_atomic_write_unit_min``: Minimum size of an atomic write request.
-- 
2.43.0

Mallikarjun Thammanavar <mallikarjunst09@gmail.com> writes:

> Fix minor spelling and grammatical issues in the ext4 atomic_writes
> documentation.
>
> Signed-off-by: Mallikarjun Thammanavar <mallikarjunst09@gmail.com>
> ---
>  Documentation/filesystems/ext4/atomic_writes.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)

Applied, thanks.

jon

On 8/19/25 5:46 AM, Mallikarjun Thammanavar wrote:
> Fix minor spelling and grammatical issues in the ext4 atomic_writes
> documentation.
> 
> Signed-off-by: Mallikarjun Thammanavar <mallikarjunst09@gmail.com>

Reviewed-by: Randy Dunlap <rdunlap@infradead.org>

Thanks.

> ---
>  Documentation/filesystems/ext4/atomic_writes.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/filesystems/ext4/atomic_writes.rst b/Documentation/filesystems/ext4/atomic_writes.rst
> index f65767df3620..b614b5ffe76b 100644
> --- a/Documentation/filesystems/ext4/atomic_writes.rst
> +++ b/Documentation/filesystems/ext4/atomic_writes.rst
> @@ -14,7 +14,7 @@ I/O) on regular files with extents, provided the underlying storage device
>  supports hardware atomic writes. This is supported in the following two ways:
>  
>  1. **Single-fsblock Atomic Writes**:
> -   EXT4's supports atomic write operations with a single filesystem block since
> +   EXT4 supports atomic write operations with a single filesystem block since
>     v6.13. In this the atomic write unit minimum and maximum sizes are both set
>     to filesystem blocksize.
>     e.g. doing atomic write of 16KB with 16KB filesystem blocksize on 64KB
> @@ -50,7 +50,7 @@ Multi-fsblock Implementation Details
>  
>  The bigalloc feature changes ext4 to allocate in units of multiple filesystem
>  blocks, also known as clusters. With bigalloc each bit within block bitmap
> -represents cluster (power of 2 number of blocks) rather than individual
> +represents a cluster (power of 2 number of blocks) rather than individual
>  filesystem blocks.
>  EXT4 supports multi-fsblock atomic writes with bigalloc, subject to the
>  following constraints. The minimum atomic write size is the larger of the fs
> @@ -189,7 +189,7 @@ The write must be aligned to the filesystem's block size and not exceed the
>  filesystem's maximum atomic write unit size.
>  See ``generic_atomic_write_valid()`` for more details.
>  
> -``statx()`` system call with ``STATX_WRITE_ATOMIC`` flag can provides following
> +``statx()`` system call with ``STATX_WRITE_ATOMIC`` flag can provide following
>  details:
>  
>   * ``stx_atomic_write_unit_min``: Minimum size of an atomic write request.

-- 
~Randy

On Tue, Aug 19, 2025 at 12:46:04PM +0000, Mallikarjun Thammanavar wrote:
> Fix minor spelling and grammatical issues in the ext4 atomic_writes
> documentation.
> 
> Signed-off-by: Mallikarjun Thammanavar <mallikarjunst09@gmail.com>

Much improved, thanks!
Reviewed-by: "Darrick J. Wong" <djwong@kernel.org>

--D

> ---
>  Documentation/filesystems/ext4/atomic_writes.rst | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/Documentation/filesystems/ext4/atomic_writes.rst b/Documentation/filesystems/ext4/atomic_writes.rst
> index f65767df3620..b614b5ffe76b 100644
> --- a/Documentation/filesystems/ext4/atomic_writes.rst
> +++ b/Documentation/filesystems/ext4/atomic_writes.rst
> @@ -14,7 +14,7 @@ I/O) on regular files with extents, provided the underlying storage device
>  supports hardware atomic writes. This is supported in the following two ways:
>  
>  1. **Single-fsblock Atomic Writes**:
> -   EXT4's supports atomic write operations with a single filesystem block since
> +   EXT4 supports atomic write operations with a single filesystem block since
>     v6.13. In this the atomic write unit minimum and maximum sizes are both set
>     to filesystem blocksize.
>     e.g. doing atomic write of 16KB with 16KB filesystem blocksize on 64KB
> @@ -50,7 +50,7 @@ Multi-fsblock Implementation Details
>  
>  The bigalloc feature changes ext4 to allocate in units of multiple filesystem
>  blocks, also known as clusters. With bigalloc each bit within block bitmap
> -represents cluster (power of 2 number of blocks) rather than individual
> +represents a cluster (power of 2 number of blocks) rather than individual
>  filesystem blocks.
>  EXT4 supports multi-fsblock atomic writes with bigalloc, subject to the
>  following constraints. The minimum atomic write size is the larger of the fs
> @@ -189,7 +189,7 @@ The write must be aligned to the filesystem's block size and not exceed the
>  filesystem's maximum atomic write unit size.
>  See ``generic_atomic_write_valid()`` for more details.
>  
> -``statx()`` system call with ``STATX_WRITE_ATOMIC`` flag can provides following
> +``statx()`` system call with ``STATX_WRITE_ATOMIC`` flag can provide following
>  details:
>  
>   * ``stx_atomic_write_unit_min``: Minimum size of an atomic write request.
> -- 
> 2.43.0
> 
>