From: Dennis Lam Date: Sun, 8 Sep 2024 17:28:42 +0000 (-0400) Subject: docs:filesystems: fix spelling and grammar mistakes in iomap design page X-Git-Tag: v6.12-rc1~118^2~6 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=b1daf3f8475fa2a4ffc1668043de738241f95d1d;p=thirdparty%2Flinux.git docs:filesystems: fix spelling and grammar mistakes in iomap design page Signed-off-by: Dennis Lam Link: https://lore.kernel.org/r/20240908172841.9616-2-dennis.lamerice@gmail.com Signed-off-by: Christian Brauner --- diff --git a/Documentation/filesystems/iomap/design.rst b/Documentation/filesystems/iomap/design.rst index f8ee3427bc1a5..e2d34085dd0e6 100644 --- a/Documentation/filesystems/iomap/design.rst +++ b/Documentation/filesystems/iomap/design.rst @@ -142,9 +142,9 @@ Definitions * **pure overwrite**: A write operation that does not require any metadata or zeroing operations to perform during either submission or completion. - This implies that the fileystem must have already allocated space + This implies that the filesystem must have already allocated space on disk as ``IOMAP_MAPPED`` and the filesystem must not place any - constaints on IO alignment or size. + constraints on IO alignment or size. The only constraints on I/O alignment are device level (minimum I/O size and alignment, typically sector size). @@ -426,7 +426,7 @@ iomap is concerned: The exact locking requirements are specific to the filesystem; for certain operations, some of these locks can be elided. -All further mention of locking are *recommendations*, not mandates. +All further mentions of locking are *recommendations*, not mandates. Each filesystem author must figure out the locking for themself. Bugs and Limitations