Re: [PATCH] Documentation: Fix spelling mistakes

Randy Dunlap
2025-09-02T19:47:44Z

On 9/2/25 12:38 PM, Ranganath V N wrote:
> Corrected a few spelling mistakes to improve the readability.
>
> Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>

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

Thanks.

> ---
> Documentation/devicetree/bindings/submitting-patches.rst | 2 +-
> Documentation/filesystems/iomap/operations.rst | 2 +-
> Documentation/virt/kvm/review-checklist.rst | 2 +-
> 3 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/submitting-patches.rst b/Documentation/devicetree/bindings/submitting-patches.rst
> index 46d0b036c97e..191085b0d5e8 100644
> --- a/Documentation/devicetree/bindings/submitting-patches.rst
> +++ b/Documentation/devicetree/bindings/submitting-patches.rst
> @@ -66,7 +66,7 @@ I. For patch submitters
> any DTS patches, regardless whether using existing or new bindings, should
> be placed at the end of patchset to indicate no dependency of drivers on
> the DTS. DTS will be anyway applied through separate tree or branch, so
> - different order would indicate the serie is non-bisectable.
> + different order would indicate the series is non-bisectable.
>
> If a driver subsystem maintainer prefers to apply entire set, instead of
> their relevant portion of patchset, please split the DTS patches into
> diff --git a/Documentation/filesystems/iomap/operations.rst b/Documentation/filesystems/iomap/operations.rst
> index 067ed8e14ef3..387fd9cc72ca 100644
> --- a/Documentation/filesystems/iomap/operations.rst
> +++ b/Documentation/filesystems/iomap/operations.rst
> @@ -321,7 +321,7 @@ The fields are as follows:
> - ``writeback_submit``: Submit the previous built writeback context.
> Block based file systems should use the iomap_ioend_writeback_submit
> helper, other file system can implement their own.
> - File systems can optionall to hook into writeback bio submission.
> + File systems can optionally hook into writeback bio submission.
> This might include pre-write space accounting updates, or installing
> a custom ``->bi_end_io`` function for internal purposes, such as
> deferring the ioend completion to a workqueue to run metadata update
> diff --git a/Documentation/virt/kvm/review-checklist.rst b/Documentation/virt/kvm/review-checklist.rst
> index debac54e14e7..053f00c50d66 100644
> --- a/Documentation/virt/kvm/review-checklist.rst
> +++ b/Documentation/virt/kvm/review-checklist.rst
> @@ -98,7 +98,7 @@ New APIs
> It is important to demonstrate your use case. This can be as simple as
> explaining that the feature is already in use on bare metal, or it can be
> a proof-of-concept implementation in userspace. The latter need not be
> - open source, though that is of course preferrable for easier testing.
> + open source, though that is of course preferable for easier testing.
> Selftests should test corner cases of the APIs, and should also cover
> basic host and guest operation if no open source VMM uses the feature.
>

--
~Randy