summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDennis Lam <dennis.lamerice@gmail.com>2024-09-08 20:28:42 +0300
committerChristian Brauner <brauner@kernel.org>2024-09-09 10:53:13 +0300
commitb1daf3f8475fa2a4ffc1668043de738241f95d1d (patch)
treec58fa6797ee0d121bd290795e7c1ed6ef8f6fda0
parent3d693c1811e3b57438dc6a4e26a420da6def09b4 (diff)
downloadlinux-b1daf3f8475fa2a4ffc1668043de738241f95d1d.tar.xz
docs:filesystems: fix spelling and grammar mistakes in iomap design page
Signed-off-by: Dennis Lam <dennis.lamerice@gmail.com> Link: https://lore.kernel.org/r/20240908172841.9616-2-dennis.lamerice@gmail.com Signed-off-by: Christian Brauner <brauner@kernel.org>
-rw-r--r--Documentation/filesystems/iomap/design.rst6
1 files changed, 3 insertions, 3 deletions
diff --git a/Documentation/filesystems/iomap/design.rst b/Documentation/filesystems/iomap/design.rst
index f8ee3427bc1a..e2d34085dd0e 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