X-Git-Url: http://git.marmaro.de/?a=blobdiff_plain;f=man%2Fmhbuild.man1;h=98fb39daa7e6dbb080b0d53ef272e60e7a1208de;hb=9cf6132a6ea29968131a000bc2fb6860affac45e;hp=5545fffcebcc3eaa3cc03d0708673733dce91169;hpb=5c43bb739797c078c3fd6aa982183e15af456d31;p=mmh

diff --git a/man/mhbuild.man1 b/man/mhbuild.man1
index 5545fff..98fb39d 100644
--- a/man/mhbuild.man1
+++ b/man/mhbuild.man1
@@ -24,7 +24,7 @@ creates multi-media messages as specified in RFC\-2045
 thru RFC\-2049.  Currently
 .B mhbuild
 only supports encodings in
-message bodies, and does not support the encoding of message headers as
+message bodies, and does support the encoding of message headers as
 specified in RFC\-2047.
 .PP
 If you specify the name of the composition file as `-',
@@ -41,10 +41,11 @@ Otherwise if the file argument to
 is the name of a valid
 composition file, and the translation is successful,
 .B mhbuild
-will replace the original file with the new MIME message.  It will rename
-the original file to start with the `,' character and end with the
-string `.orig', e.g., if you are editing the file `draft',
-it will be renamed to `,draft.orig'.  This allows you to easily
+will replace the original file with the new MIME message.
+It will preserve the original file under the same name with `.orig'
+appended.
+E.g., if you are editing the file `draft', its original contents
+it will be preserved as `draft.orig'.  This allows you to easily
 recover the
 .B mhbuild
 input file.