Re: [PATCH v2 4/9] docs: device-mapper: fixed spelling mistakes in documentation

[Mikulas Patocka <mpatocka@redhat.com>]

Applied, thanks.

Mikulas



On Wed, 13 Aug 2025, Soham Metha wrote:

> found/fixed the following typos
> 
> - flushs -> flushes
> - explicitely -> explicitly
> 
> in `Documentation/admin-guide/device-mapper/delay.rst`, and
> 
> - approriate -> appropriate
> 
> in `Documentation/admin-guide/device-mapper/vdo-design.rst`
> 
> Signed-off-by: Soham Metha <sohammetha01@gmail.com>
> ---
>  Documentation/admin-guide/device-mapper/delay.rst      | 8 ++++----
>  Documentation/admin-guide/device-mapper/vdo-design.rst | 2 +-
>  2 files changed, 5 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/admin-guide/device-mapper/delay.rst b/Documentation/admin-guide/device-mapper/delay.rst
> index 4d667228e744..a1e673c0e782 100644
> --- a/Documentation/admin-guide/device-mapper/delay.rst
> +++ b/Documentation/admin-guide/device-mapper/delay.rst
> @@ -3,7 +3,7 @@ dm-delay
>  ========
>  
>  Device-Mapper's "delay" target delays reads and/or writes
> -and/or flushs and optionally maps them to different devices.
> +and/or flushes and optionally maps them to different devices.
>  
>  Arguments::
>  
> @@ -18,7 +18,7 @@ Table line has to either have 3, 6 or 9 arguments:
>     to write and flush operations on optionally different write_device with
>     optionally different sector offset
>  
> -9: same as 6 arguments plus define flush_offset and flush_delay explicitely
> +9: same as 6 arguments plus define flush_offset and flush_delay explicitly
>     on/with optionally different flush_device/flush_offset.
>  
>  Offsets are specified in sectors.
> @@ -40,7 +40,7 @@ Example scripts
>  	#!/bin/sh
>  	#
>  	# Create mapped device delaying write and flush operations for 400ms and
> -	# splitting reads to device $1 but writes and flushs to different device $2
> +	# splitting reads to device $1 but writes and flushes to different device $2
>  	# to different offsets of 2048 and 4096 sectors respectively.
>  	#
>  	dmsetup create delayed --table "0 `blockdev --getsz $1` delay $1 2048 0 $2 4096 400"
> @@ -48,7 +48,7 @@ Example scripts
>  ::
>  	#!/bin/sh
>  	#
> -	# Create mapped device delaying reads for 50ms, writes for 100ms and flushs for 333ms
> +	# Create mapped device delaying reads for 50ms, writes for 100ms and flushes for 333ms
>  	# onto the same backing device at offset 0 sectors.
>  	#
>  	dmsetup create delayed --table "0 `blockdev --getsz $1` delay $1 0 50 $2 0 100 $1 0 333"
> diff --git a/Documentation/admin-guide/device-mapper/vdo-design.rst b/Documentation/admin-guide/device-mapper/vdo-design.rst
> index 3cd59decbec0..faa0ecd4a5ae 100644
> --- a/Documentation/admin-guide/device-mapper/vdo-design.rst
> +++ b/Documentation/admin-guide/device-mapper/vdo-design.rst
> @@ -600,7 +600,7 @@ lock and return itself to the pool.
>  All storage within vdo is managed as 4KB blocks, but it can accept writes
>  as small as 512 bytes. Processing a write that is smaller than 4K requires
>  a read-modify-write operation that reads the relevant 4K block, copies the
> -new data over the approriate sectors of the block, and then launches a
> +new data over the appropriate sectors of the block, and then launches a
>  write operation for the modified data block. The read and write stages of
>  this operation are nearly identical to the normal read and write
>  operations, and a single data_vio is used throughout this operation.
> -- 
> 2.34.1
>