Linux kernel mirror (for testing) git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
kernel os linux

Documentation: Fix spelling mistakes

Corrected a few spelling mistakes to improve the readability.

Signed-off-by: Ranganath V N <vnranganath.20@gmail.com>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
Reviewed-by: Randy Dunlap <rdunlap@infradead.org>
Signed-off-by: Jonathan Corbet <corbet@lwn.net>
Link: https://lore.kernel.org/r/20250902193822.6349-1-vnranganath.20@gmail.com

authored by

Ranganath V N and committed by
Jonathan Corbet
a4c2ff6e b65988af

+3 -3
+1 -1
Documentation/devicetree/bindings/submitting-patches.rst
··· 66 66 any DTS patches, regardless whether using existing or new bindings, should 67 67 be placed at the end of patchset to indicate no dependency of drivers on 68 68 the DTS. DTS will be anyway applied through separate tree or branch, so 69 - different order would indicate the serie is non-bisectable. 69 + different order would indicate the series is non-bisectable. 70 70 71 71 If a driver subsystem maintainer prefers to apply entire set, instead of 72 72 their relevant portion of patchset, please split the DTS patches into
+1 -1
Documentation/filesystems/iomap/operations.rst
··· 321 321 - ``writeback_submit``: Submit the previous built writeback context. 322 322 Block based file systems should use the iomap_ioend_writeback_submit 323 323 helper, other file system can implement their own. 324 - File systems can optionall to hook into writeback bio submission. 324 + File systems can optionally hook into writeback bio submission. 325 325 This might include pre-write space accounting updates, or installing 326 326 a custom ``->bi_end_io`` function for internal purposes, such as 327 327 deferring the ioend completion to a workqueue to run metadata update
+1 -1
Documentation/virt/kvm/review-checklist.rst
··· 98 98 It is important to demonstrate your use case. This can be as simple as 99 99 explaining that the feature is already in use on bare metal, or it can be 100 100 a proof-of-concept implementation in userspace. The latter need not be 101 - open source, though that is of course preferrable for easier testing. 101 + open source, though that is of course preferable for easier testing. 102 102 Selftests should test corner cases of the APIs, and should also cover 103 103 basic host and guest operation if no open source VMM uses the feature. 104 104