Fix various typos and stylistic

diff --git a/doc/faq.texi b/doc/faq.texi
index 1e399a0b2366ee68fececc93785982a8174dd3da..e494e88500f7b8995301ef751b9764a25ac81242 100644 (file)
--- a/doc/faq.texi
+++ b/doc/faq.texi
@@ -14,13 +14,13 @@ them do not apply.
 @itemize
 @item Aggregate targets and willing to be out-of-date ones just must not
   produce empty output files. @command{apenwarr/*}, @command{redo-c} and
 @itemize
 @item Aggregate targets and willing to be out-of-date ones just must not
   produce empty output files. @command{apenwarr/*}, @command{redo-c} and

-  @command{goredo} implementations consider non existing file as an
+  @command{goredo} implementations treat non existing file as an

   out-of-date target
 @item If you really wish to produce an empty target file, just touch @file{$3}
 @end itemize
 
   out-of-date target
 @item If you really wish to produce an empty target file, just touch @file{$3}
 @end itemize
 

-Those who create an empty file if no @file{stdout} was written -- failed
-implementation.
+Those who create an empty file if no @file{stdout} was written -- are
+failed implementations.

 
 redo is a tool to help people. Literally all targets can be safely
 @code{redo-stamp < $3}-ed, reducing false positive out-of-dates. Of
 
 redo is a tool to help people. Literally all targets can be safely
 @code{redo-stamp < $3}-ed, reducing false positive out-of-dates. Of


@@ -28,11 +28,11 @@ course, with the correct @file{stdout}/@file{$3} working and placing
 necessary results in @file{$3}, instead of just silently feeding them in
 @command{redo-stamp}.
 
 necessary results in @file{$3}, instead of just silently feeding them in
 @command{redo-stamp}.
 

-redo implementations are already automatically record -ifchange on
+redo implementations already automatically record -ifchange on

 @file{.do} files and -ifcreate on non-existing @file{.do} files. So why
 they can not record @command{redo-stamp} the same way implicitly? No,
 @file{.do} files and -ifcreate on non-existing @file{.do} files. So why
 they can not record @command{redo-stamp} the same way implicitly? No,

-Zen of Python does not applicable there, because -ifchange/-ifcreate
-contradict it already.
+Zen of Python is not applicable there, because -ifchange/-ifcreate
+contradicts it already.

 
 Modern cryptographic hash algorithms and CPUs are so fast, that even all
 read and writes to or from hard drive arrays can be easily checksummed
 
 Modern cryptographic hash algorithms and CPUs are so fast, that even all
 read and writes to or from hard drive arrays can be easily checksummed