dedup

commit 1f0d8ef4ab43be2906c3a2b3be7d4a70a3b138b7
parent 49409939d57a74f748c31a374b98232300f1ebf8
Author: sin <sin@2f30.org>
Date:   Sat,  2 Mar 2019 13:48:54 +0000

Update wording in README

Diffstat:
M
README
 | 
5
+++--

1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/README b/README
@@ -5,7 +5,8 @@ To use dedup you have to first initialize the repository.
     dedup -r ~/bak -i
 
 dedup only handles a single file at a time, so using tar is advised.
-For example, to dedup a tar file you can invoke dedup as follows:
+For example, to dedup a directory file you can invoke dedup as
+follows:
 
     tar -c ~/dir | dedup -r ~/bak -m "$(date)"
 
@@ -13,7 +14,7 @@ This will create .{cache,snapshots,store} files in the ~/bak
 directory.  The store file contains all the unique blocks.  The
 snapshots file contains all the revisions of files that have been
 deduplicated.  Each revision is identified by its SHA256 hash.  The
-cache file is only used to speed up block comparison.
+cache file is only used to speed up block hash comparison.
 
 To list all known revisions run: