X-Git-Url: http://www.git.cypherpunks.ru/?p=goredo.git;a=blobdiff_plain;f=doc%2Ffaq.texi;h=16fadafa01bef6604c7be428c6a64e5d1ac8e483;hp=9b909a653bcdfddeeaa4af907eedd19e51777938;hb=5ca39bfc0b769607db3f84213fc7f16f0c4019fa;hpb=f85b073ee154a49bbd7ca0b6b2a68add4968700c

diff --git a/doc/faq.texi b/doc/faq.texi
index 9b909a6..16fadaf 100644
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -42,7 +42,7 @@ and transparently compressed, as ZFS with LZ4/Zstandard and
 Skein/BLAKE[23] algorithms demonstrate us.
 
 @command{goredo} includes @command{redo-stamp}, that really records the
-stamp in the @file{.dep} file, but it does not play any role later. It
+stamp in the @file{.rec} file, but it does not play any role later. It
 is stayed just for compatibility.
 
 @section Can removed .do lead to permanent errors of its non existence?
@@ -52,7 +52,7 @@ assume that @file{.do}-less target now is an ordinary source-file? I
 have no confidence in such behaviour. So it is user's decision how to
 deal with it, probably it was just his inaccuracy mistake. If you really
 want to get rid of that dependency knowledge for @file{foo/bar} target,
-then just remove @file{foo/.redo/bar.dep}.
+then just remove @file{foo/.redo/bar.rec}.
 
 @section Does redo-always always rebuilds target?