From de06b1d957bdad592fff87e845d27d40cfcbd694 Mon Sep 17 00:00:00 2001
From: Daniel Baumann <mail@daniel-baumann.ch>
Date: Sat, 7 Nov 2015 12:52:32 +0100
Subject: Adding upstream version 1.18~pre1.

Signed-off-by: Daniel Baumann <mail@daniel-baumann.ch>
---
 doc/lziprecover.1    |  4 ++--
 doc/lziprecover.info | 28 ++++++++++++++--------------
 doc/lziprecover.texi | 10 +++++-----
 3 files changed, 21 insertions(+), 21 deletions(-)

(limited to 'doc')

diff --git a/doc/lziprecover.1 b/doc/lziprecover.1
index b420b76..99b61dd 100644
--- a/doc/lziprecover.1
+++ b/doc/lziprecover.1
@@ -1,5 +1,5 @@
 .\" DO NOT MODIFY THIS FILE!  It was generated by help2man 1.46.1.
-.TH LZIPRECOVER "1" "May 2015" "lziprecover 1.17" "User Commands"
+.TH LZIPRECOVER "1" "June 2015" "lziprecover 1.18-pre1" "User Commands"
 .SH NAME
 lziprecover \- recovers data from damaged lzip files
 .SH SYNOPSIS
@@ -30,7 +30,7 @@ send decompressed output to standard output
 decompress
 .TP
 \fB\-D\fR, \fB\-\-range\-decompress=\fR<range>
-decompress only a range of bytes (N\-M)
+decompress a range of bytes (N\-M) to stdout
 .TP
 \fB\-f\fR, \fB\-\-force\fR
 overwrite existing output files
diff --git a/doc/lziprecover.info b/doc/lziprecover.info
index cb9517a..654e60c 100644
--- a/doc/lziprecover.info
+++ b/doc/lziprecover.info
@@ -12,7 +12,7 @@ File: lziprecover.info,  Node: Top,  Next: Introduction,  Up: (dir)
 Lziprecover Manual
 ******************
 
-This manual is for Lziprecover (version 1.17, 28 May 2015).
+This manual is for Lziprecover (version 1.18-pre1, 30 June 2015).
 
 * Menu:
 
@@ -274,7 +274,7 @@ files::), if at least one backup copy of the file is made.
 separate media.
 
    How does lzip compare with gzip and bzip2 with respect to data
-safety?  Lets suppose that you made a backup copy of your valuable
+safety?  Lets suppose that you made a backup of your valuable
 scientific data, compressed it, and stored two copies on separate
 media. Years later you notice that both copies are corrupt.
 
@@ -652,18 +652,18 @@ Concept index
 
 Tag Table:
 Node: Top231
-Node: Introduction1208
-Node: Invoking lziprecover4304
-Node: Data safety9737
-Node: Repairing files11666
-Node: Merging files13568
-Node: File names15409
-Node: File format15873
-Node: Examples18277
-Ref: ddrescue-example19523
-Node: Unzcrash20779
-Node: Problems23333
-Node: Concept index23885
+Node: Introduction1214
+Node: Invoking lziprecover4310
+Node: Data safety9743
+Node: Repairing files11667
+Node: Merging files13569
+Node: File names15410
+Node: File format15874
+Node: Examples18278
+Ref: ddrescue-example19524
+Node: Unzcrash20780
+Node: Problems23334
+Node: Concept index23886
 
 End Tag Table
 
diff --git a/doc/lziprecover.texi b/doc/lziprecover.texi
index 3f6e0aa..29045e7 100644
--- a/doc/lziprecover.texi
+++ b/doc/lziprecover.texi
@@ -6,8 +6,8 @@
 @finalout
 @c %**end of header
 
-@set UPDATED 28 May 2015
-@set VERSION 1.17
+@set UPDATED 30 June 2015
+@set VERSION 1.18-pre1
 
 @dircategory Data Compression
 @direntry
@@ -302,9 +302,9 @@ The only remedy for total device failure is storing backup copies in
 separate media.
 
 How does lzip compare with gzip and bzip2 with respect to data safety?
-Lets suppose that you made a backup copy of your valuable scientific
-data, compressed it, and stored two copies on separate media. Years
-later you notice that both copies are corrupt.
+Lets suppose that you made a backup of your valuable scientific data,
+compressed it, and stored two copies on separate media. Years later you
+notice that both copies are corrupt.
 
 If you compressed with gzip and both copies suffer any damage in the
 data stream, even if it is just one altered bit, the original data can't
-- 
cgit v1.2.3