Clarify $write_bcc documentation.

The wording was ambiguous, and could give the impression that a
message, if fcc'ed, would contain the Bcc header when sent too.

1 files changed, 2 insertions, 1 deletions

diff --git a/init.h b/init.h
index 89e85bfb..bf7f1288 100644
--- a/init.h
+++ b/init.h
@@ -4348,7 +4348,8 @@ struct option_t MuttVars[] = {
   ** header in this case.
   ** .pp
   ** Note this option only affects the sending of messages.  Fcc'ed
-  ** messages will always write the ``Bcc:'' header if one exists.
+  ** copies of a message will always contain the ``Bcc:'' header if
+  ** one exists.
   */
   { "write_inc",	DT_NUM,	 R_NONE, {.p=&WriteInc}, {.l=10} },
   /*