[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <b03394a2-eca7-6c39-6ab8-d3a7ae1c7233@redhat.com>
Date: Mon, 11 Aug 2025 13:22:18 +0200 (CEST)
From: Mikulas Patocka <mpatocka@...hat.com>
To: Shubham Sharma <slopixelz@...il.com>
cc: agk@...hat.com, snitzer@...nel.org, corbet@....net, msakai@...hat.com,
dm-devel@...ts.linux.dev, linux-doc@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH] docs: device-mapper :Fix typos in delay.rst and
vdo-design.rst
Applied, thanks.
Mikulas
On Sun, 10 Aug 2025, Shubham Sharma wrote:
> Fixed the following typos in device-mapper documentation:
> - explicitely -> explicitly
> - approriate -> appropriate
>
> Signed-off-by: Shubham Sharma <slopixelz@...il.com>
> ---
> Documentation/admin-guide/device-mapper/delay.rst | 2 +-
> Documentation/admin-guide/device-mapper/vdo-design.rst | 2 +-
> 2 files changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/admin-guide/device-mapper/delay.rst b/Documentation/admin-guide/device-mapper/delay.rst
> index 4d667228e744..982136160d6f 100644
> --- a/Documentation/admin-guide/device-mapper/delay.rst
> +++ b/Documentation/admin-guide/device-mapper/delay.rst
> @@ -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.
> 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.43.0
>
Powered by blists - more mailing lists