Skip to content

Commit b1daf3f

Browse files
Dennis Lambrauner
authored andcommitted
docs:filesystems: fix spelling and grammar mistakes in iomap design page
Signed-off-by: Dennis Lam <[email protected]> Link: https://lore.kernel.org/r/[email protected] Signed-off-by: Christian Brauner <[email protected]>
1 parent 3d693c1 commit b1daf3f

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

Documentation/filesystems/iomap/design.rst

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -142,9 +142,9 @@ Definitions
142142
* **pure overwrite**: A write operation that does not require any
143143
metadata or zeroing operations to perform during either submission
144144
or completion.
145-
This implies that the fileystem must have already allocated space
145+
This implies that the filesystem must have already allocated space
146146
on disk as ``IOMAP_MAPPED`` and the filesystem must not place any
147-
constaints on IO alignment or size.
147+
constraints on IO alignment or size.
148148
The only constraints on I/O alignment are device level (minimum I/O
149149
size and alignment, typically sector size).
150150

@@ -426,7 +426,7 @@ iomap is concerned:
426426

427427
The exact locking requirements are specific to the filesystem; for
428428
certain operations, some of these locks can be elided.
429-
All further mention of locking are *recommendations*, not mandates.
429+
All further mentions of locking are *recommendations*, not mandates.
430430
Each filesystem author must figure out the locking for themself.
431431

432432
Bugs and Limitations

0 commit comments

Comments
 (0)