From ef07687826abc1d1d7263c074c11bb1a7fe83f8b Mon Sep 17 00:00:00 2001 From: ckolivas Date: Wed, 11 Jan 2012 14:10:53 +1100 Subject: [PATCH] Fix typos courtesy of A. Costa agcosta@gis.net --- man/lrzip.1 | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/man/lrzip.1 b/man/lrzip.1 index c5a8fd0..6e5598d 100644 --- a/man/lrzip.1 +++ b/man/lrzip.1 @@ -86,7 +86,7 @@ However the file written to disk may be corrupted for other reasons to do with other userspace problems such as faulty library versions, drivers, hardware failure and so on. Enabling this option will make lrzip perform an md5 hash check on the file that's written to disk. When the archive has the md5 value -stored in it, it is compared to this. Otherwise it is compard to the value +stored in it, it is compared to this. Otherwise it is compared to the value calculated during decompression. This offers an extra guarantee that the file written is the same as the original archived. .IP @@ -115,7 +115,7 @@ This shows the md5 hash value calculated on compressing or decompressing an lrzip archive. By default all compression has the md5 value calculated and stored in all archives since version 0.560. On decompression, when an md5 value has been found, it will be calculated and used for integrity checking. -If the md5 value is not stored in the archive, it will not be calcuated unless +If the md5 value is not stored in the archive, it will not be calculated unless explicitly specified with this option, or check integrity (see below) has been requested. .IP