Direct bug reports to Wine bugzilla. Some other minor documentation

documentation/configuring.sgml

@@ -929,7 +929,9 @@ OPTIONAL:
         <title>What If It Doesn't Work?</title>
         <para>
           There is always a chance that things will go wrong. If the
-          unthinkable happens,  try the newsgroup,
+          unthinkable happens report the problem to
+	  <ulink url="http://bugs.winehq.com/">Wine Bugzilla</ulink>,
+	  try the newsgroup
           <systemitem>comp.emulators.ms-windows.wine</systemitem>,
 	  or the IRCnet channel <systemitem>#WineHQ</systemitem> found on
           irc.stealth.net:6668,	 or connected servers.

documentation/wine.man.in

@@ -300,7 +300,7 @@ of the authors, please see the file
 in the top-level directory of the source distribution.
 .SH COPYRIGHT
 .B wine
-can be distributed under the terms of the X11 license. A copy of the
+can be distributed under the terms of the LGPL license. A copy of the
 license is in the file
 .B LICENSE
 in the top-level directory of the source distribution.
@@ -310,16 +310,16 @@ A status report on many applications is available from
 .I http://www.winehq.com/Apps.
 Please add entries to this list for applications you currently run.
 .PP
-Bug reports and successes may be posted to 
-.I comp.emulators.ms-windows.wine.
+Bug reports may be posted to Wine Bugzilla
+.I http://bugs.winehq.com
 If you want to post a bug report, please read the file
 .I documentation/bugs.sgml
 in the 
 .B wine 
-source to see what information is necessary (FIXME: outdated).
+source to see what information is necessary
 .PP
-For problems and suggestions with this manpage, please send a note to
-James Juran <jrj120@psu.edu>.
+Problems and suggestions with this manpage please also report to
+.I http://bugs.winehq.com
 .SH AVAILABILITY
 The most recent public version of 
 .B wine
@@ -353,8 +353,8 @@ For further information about
 .B wine
 development, you might want to subscribe to the 
 .B wine 
-"cvs", "devel" and "patches" mailing lists at
-.I http://www.winehq.com/dev.html#ml.
+mailing lists at
+.I http://www.winehq.com/development/#ml
 .SH FILES
 .PD 0
 .TP

tools/bug_report.pl

@@ -74,8 +74,10 @@ if ($debuglevel < 3) {
 	two files. The first one has everything asked for by the bugreports guide;
 	the second has *all* of the debug output, which can go to thousands of
 	lines.
-	To (hopefully) get the bug fixed, attach the first file to a messsage
-	sent to the comp.emulators.ms-windows.wine newsgroup. The developers
+	To (hopefully) get the bug fixed, report it to the project
+	bug tracking system at http://bugs.winehq.com.
+	Attach the first file to the bug description.
+	Also include detailed description of the problem. The developers
 	might ask you for "the last X lines from the report". If so, just
 	provide the output of the following command:
 	    gzip -d (output file) | tail -n (X) > outfile
@@ -564,8 +566,9 @@ $dbgoutfile.gz
 Note that it is $dbgoutfile.gz, since I compressed it with gzip for you.
 };
 $var30 = qq{
-Having problems with the script? Tell the wine newsgroup
-(comp.emulators.ms-windows.wine).
+Having problems with the script?
+Submit a bug report to Wine bugtracking system at http://bugs.winehq.com or
+tell the wine newsgroup (comp.emulators.ms-windows.wine).
 };
 print do_var($var22);
 print do_var($var28) if $outfile ne "no file";