Fix some typos. In particular, it's bug tracking system, not buck

tracking system.  Oh well.

1 files changed, 26 insertions, 16 deletions

diff --git a/doc/muttbug.man b/doc/muttbug.man
index a78c5fcf..48de301a 100644
--- a/doc/muttbug.man
+++ b/doc/muttbug.man
@@ -69,7 +69,7 @@ package on your system, and suggest to file the bug against the
 .BR mutt (1)
 and Debian bug tracking systems.  This option was added since the 
 .BR mutt (1)
-project uses another instantiation of the Debian buck tracking
+project uses another instantiation of the Debian bug tracking
 system, so submitting bugs against both systems in one pass is
 simple.
 .PP
@@ -77,15 +77,17 @@ You are then dropped into your favorite editor as determined by the
 .B EDITOR
 and
 .B VISUAL
-environment variables.  Please give us details about the problem in
-the empty space below the line reading \(lqPlease type your report
-below this line\(rq.  We are most interested in precise information
-on what symptoms you observe and what steps may be used to reproduce
-the bug.  Chances are that problems which can easily be reproduced
-will be fixed quickly.  So please take some time when filling out
-this part of the template.
-.PP
-The rest of the template contains various kinds of information
+environment variables.  
+.PP
+Please give us details about the problem in the empty space below
+the line reading \(lqPlease type your report below this line\(rq.
+We are most interested in precise information on what symptoms you
+observe and what steps may be used to reproduce the bug.  Chances
+are that problems which can easily be reproduced will be fixed
+quickly.  So please take some time when filling out this part of the
+template.
+.PP
+The remainder of the template contains various kinds of information
 gathered from your system, including output of the
 .BR uname (1)
 command, output from
@@ -112,11 +114,16 @@ information about the bug, you can just send it to the address
 Later, you will most likely receive questions from the developers
 about the problem you observed, and you will eventually be informed
 that your bug report has been closed.  This means that the bug has
-been fixed at least in the 
+been fixed at least in the
 .BR cvs (1)
-repository.   If the answers you receive don't satisfy you, don't
-hesitate to contact the developers directly under 
+repository.  If the answers you receive don't satisfy you, don't
+hesitate to contact the developers directly under
 .BR mutt-dev@mutt.org.
+.PP
+You can also browse your bug report and all additional information
+and replies connected to it using the bug tracking system's Web
+interface under the following URL:
+http://bugs.guug.de/
 .SH
 ENVIRONMENT
 .PP
@@ -130,7 +137,7 @@ Your login name.  If the
 .B EMAIL
 environment variable isn't set, this will be used instead to send
 you a copy of the report.  Setting the sender will be left to 
-.BR sendmail (8)
+.BR sendmail (1)
 on your system.
 .IP "REPLYTO"
 If set, the bug report will contain a Reply-To header with the
@@ -159,11 +166,14 @@ will be used to edit the bug report.
 .SH 
 SEE ALSO
 .PP
+.BR dbx (1),
+.BR gdb (1),
+.BR lynx (1),
 .BR mutt (1),
 .BR muttrc (5),
 .BR sdb (1),
-.BR gdb (1),
-.BR dbx (1),
+.BR sendmail (1),
+.BR uname (1),
 .BR vi (1)
 .PP
 The mutt bug tracking system: http://bugs.guug.de/