[PATCH 27/53] docs: filesystems: f2fs.rst: avoid using UTF-8 chars
From: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Date: 2021-05-10 10:34:24
Also in:
linux-f2fs-devel, lkml
Subsystem:
documentation, f2fs file system, the rest · Maintainers:
Jonathan Corbet, Jaegeuk Kim, Chao Yu, Linus Torvalds
While UTF-8 characters can be used at the Linux documentation,
the best is to use them only when ASCII doesn't offer a good replacement.
So, replace the occurences of the following UTF-8 characters:
- U+2013 ('–'): EN DASH
- U+201c ('“'): LEFT DOUBLE QUOTATION MARK
- U+201d ('”'): RIGHT DOUBLE QUOTATION MARK
Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
---
Documentation/filesystems/f2fs.rst | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/filesystems/f2fs.rst b/Documentation/filesystems/f2fs.rst
index 992bf91eeec8..19d2cf477fc3 100644
--- a/Documentation/filesystems/f2fs.rst
+++ b/Documentation/filesystems/f2fs.rst@@ -42,7 +42,7 @@ areas on disk for fast writing, we divide the log into segments and use a segment cleaner to compress the live information from heavily fragmented segments." from Rosenblum, M. and Ousterhout, J. K., 1992, "The design and implementation of a log-structured file system", ACM Trans. Computer Systems -10, 1, 26–52. +10, 1, 26-52. Wandering Tree Problem ----------------------
@@ -86,8 +86,8 @@ Flash Awareness Wandering Tree Problem ---------------------- -- Use a term, “node”, that represents inodes as well as various pointer blocks -- Introduce Node Address Table (NAT) containing the locations of all the “node” +- Use a term, "node", that represents inodes as well as various pointer blocks +- Introduce Node Address Table (NAT) containing the locations of all the "node" blocks; this will cut off the update propagation. Cleaning Overhead
--
2.30.2