From: David Tardon Date: Sat, 23 Dec 2023 17:26:34 +0000 (+0100) Subject: man: use better-fitting markup X-Git-Tag: v256-rc1~1390^2~4 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=28ed1ba9bd54cfc564a6356f577040faae252325;p=thirdparty%2Fsystemd.git man: use better-fitting markup --- diff --git a/man/veritytab.xml b/man/veritytab.xml index e58edf1a506..bdeaebe02c0 100644 --- a/man/veritytab.xml +++ b/man/veritytab.xml @@ -48,12 +48,12 @@ This is based on crypttab(5). below /dev/mapper/. The second field contains a path to the underlying block data device, or a specification of a block device via - UUID= followed by the UUID. + UUID= followed by the UUID. The third field contains a path to the underlying block hash device, or a specification of a block device via - UUID= followed by the UUID. + UUID= followed by the UUID. - The fourth field is the roothash in hexadecimal. + The fourth field is the roothash in hexadecimal. The fifth field, if present, is a comma-delimited list of options. The following options are recognized: @@ -137,9 +137,9 @@ This is based on crypttab(5). Defines what to do if a data verity problem is detected (data corruption). Without these - options kernel fails the IO operation with I/O error. With --ignore-corruption option the - corruption is only logged. With --restart-on-corruption or - --panic-on-corruption the kernel is restarted (panicked) immediately. + options kernel fails the IO operation with I/O error. With option the + corruption is only logged. With or + the kernel is restarted (panicked) immediately. (You have to provide way how to avoid restart loops.)