This patch fixes two minor typos in Documentation/filesystems/f2fs.rst:
- "ramdom" → "random"
- "reenable" → "re-enable"
The changes improve spelling and consistency in the documentation.
These issues were identified using the 'codespell' tool with the
following command:
$ find Documentation/ -path Documentation/translations -prune -o \
-name '*.rst' -print | xargs codespell
Signed-off-by: Yuanye Ma <[email protected]>
---
Documentation/filesystems/f2fs.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/filesystems/f2fs.rst
b/Documentation/filesystems/f2fs.rst
index 440e4ae74e44..8eeb7ea14f61 100644
--- a/Documentation/filesystems/f2fs.rst
+++ b/Documentation/filesystems/f2fs.rst
@@ -218,7 +218,7 @@ mode=%s Control block allocation mode
which supports "adaptive"
fragmentation/after-GC situation itself. The
developers use these
modes to understand filesystem fragmentation/after-GC
condition well,
and eventually get some insights to handle them better.
- In "fragment:segment", f2fs allocates a new segment in
ramdom
+ In "fragment:segment", f2fs allocates a new segment in
random
position. With this, we can simulate the after-GC
condition.
In "fragment:block", we can scatter block allocation
with
"max_fragment_chunk" and "max_fragment_hole" sysfs
nodes.
@@ -261,7 +261,7 @@ test_dummy_encryption=%s
The argument may be either "v1" or "v2", in order to
select the corresponding fscrypt policy version.
checkpoint=%s[:%u[%]] Set to "disable" to turn off checkpointing. Set to
"enable"
- to reenable checkpointing. Is enabled by default. While
+ to re-enable checkpointing. Is enabled by default.
While
disabled, any unmounting or unexpected shutdowns will
cause
the filesystem contents to appear as they did when the
filesystem was mounted with that option.
--
2.48.1
_______________________________________________
Linux-f2fs-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel
