Corrected minor errors in text related to $forward_attachments.

diff --git a/doc/manual.xml.head b/doc/manual.xml.head
index e34f1be4c967490ebb1ce8a3253cbc25f455e661..1bb128021f7504e46b21c2f541148a36571c4097 100644 (file)
--- a/doc/manual.xml.head
+++ b/doc/manual.xml.head
@@ -1795,7 +1795,7 @@ linkend="mime-forward">$mime_forward</link>=<quote>no</quote> and
 linkend="forward-decode">$forward_decode</link>=<quote>yes</quote>) is
 to use standard inline forwarding.  In that mode all text-decodable
 parts are included in the new message body.  Other attachments from
-the original email can also attached to the new message, based on the
+the original email can also be attached to the new message, based on the
 quadoption <link
 linkend="forward-attachments">$forward_attachments</link>.
 </para>

diff --git a/send.c b/send.c
index c04910cdade5f222458ce0e49d9188ee5e2ec219..b06ecd48871e19645d8e0375802e9206325d2576 100644 (file)
--- a/send.c
+++ b/send.c
@@ -431,9 +431,9 @@ static int inline_forward_attachments (CONTEXT *ctx, HEADER *cur,
            This is the prompt for $forward_attachments.
            When inline forwarding ($mime_forward answered "no"), this prompts
            whether to add non-decodable attachments from the original email.
-           Text/plain parts and the like will be already be included in the
+           Text/plain parts and the like will already be included in the
            message contents, but other attachment, such as PDF files, will also
-           be added as attachments to the new mail, is this is answered yes.
+           be added as attachments to the new mail, if this is answered yes.
         */
                                       _("Forward attachments?"));
         if (*forwardq != MUTT_YES)