From ef3116b5d4b9f12ae9f0fc25c8b40a04712c6d56 Mon Sep 17 00:00:00 2001 From: Zbigniew Jędrzejewski-Szmek Date: Wed, 8 Feb 2017 22:53:16 -0500 Subject: man: add more commas for clarify and reword a few sentences --- man/systemd-nspawn.xml | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'man/systemd-nspawn.xml') diff --git a/man/systemd-nspawn.xml b/man/systemd-nspawn.xml index b8cae62818..a14992f0d9 100644 --- a/man/systemd-nspawn.xml +++ b/man/systemd-nspawn.xml @@ -256,14 +256,14 @@ Takes a data integrity (dm-verity) root hash specified in hexadecimal. This option enables data integrity checks using dm-verity, if the used image contains the appropriate integrity data (see above). The - specified hash must match the root hash of integrity data, and is usually at least 256bits (and hence 64 + specified hash must match the root hash of integrity data, and is usually at least 256 bits (and hence 64 formatted hexadecimal characters) long (in case of SHA256 for example). If this option is not specified, but the image file carries the user.verity.roothash extended file attribute (see xattr7), then the root hash is read from it, also as formatted hexadecimal characters. If the extended file attribute is not found (or - not supported by the underlying file system), but a file with the .roothash suffix is - found next to the image file, bearing otherwise the same name the root hash is read from it and automatically - used (again, as formatted hexadecimal characters). + is not supported by the underlying file system), but a file with the .roothash suffix is + found next to the image file, bearing otherwise the same name, the root hash is read from it and automatically + used, also as formatted hexadecimal characters. -- cgit v1.2.3