From 54155f42ce7663d65f6b9ce5c07995e2bf14dc8b Mon Sep 17 00:00:00 2001
From: Stephan Bosch <stephan@rename-it.nl>
Date: Thu, 12 Feb 2009 22:02:27 +0100
Subject: [PATCH] Minor changes to the sievec man page.

---
 doc/man/sievec.1 | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/doc/man/sievec.1 b/doc/man/sievec.1
index 51062cc7c..049be8632 100644
--- a/doc/man/sievec.1
+++ b/doc/man/sievec.1
@@ -38,9 +38,9 @@ is a directory.
 .PP
 The \fBsievec\fP command is also useful to verify Sieve scripts before using. Additionally, with 
 the \fB-d\fP option it can output a textual (and thus human-readable) dump of the generated Sieve
-code to the specified file in stead of the binary. The output is then identical to what the 
-\fBsieved\fP(1) command produces for a stored binary file. This output is mainly useful to find 
-bugs in the compiler that yield corrupt binaries.
+code to the specified file. The output is then identical to what the \fBsieved\fP(1) command produces
+for a stored binary file. This output is mainly useful to find bugs in the compiler that yield corrupt 
+binaries.
 .SH OPTIONS
 .TP 
 \fB-d\fP 
@@ -48,7 +48,7 @@ Don't write the binary to \fIoutfile\fP, but write a textual dump of the binary
 stead. In this context, the \fIoutfile\fP value '-' has special meaning: it causes the the textual 
 dump to be written to \fBstdout\fP. The \fIoutfile\fP argument may also be omitted, which has 
 the same effect as '-'. The output is identical to what the \fBsieved\fP(1) command produces for 
-a compiled Sieve binary file. Note that this option is not allowed when the \fIscriptfile\fP argument
+a compiled Sieve binary file. Note that this option is not allowed when the \fIoutfile\fP argument
 is a directory.
 .TP
 \fB-x\fP "\fIextension extension ...\fP"
-- 
GitLab