3 files changed, 16 insertions, 16 deletions
diff --git a/contrib/bugzilla-submit/README b/contrib/bugzilla-submit/README
index 08bc3d85c..f9e74b9d4 100644
--- a/contrib/bugzilla-submit/README
+++ b/contrib/bugzilla-submit/README
@@ -1,10 +1,10 @@
-Bug-Bugzilla
-============
+bugzilla-submit
+===============
 
 Authors: Christian Reis <kiko@async.com.br>
          Eric Raymond <esr@thyrsus.com>
 
-Bug-Bugzilla is a simple Python program that creates bugs in a Bugzilla
+bugzilla-submit is a simple Python program that creates bugs in a Bugzilla
 instance. It takes as input text resembling message headers (RFC-822
 formatted) via standard input, or optionally a number of commandline
 parameters. It communicates using HTTP, which allows it to work over a
@@ -23,10 +23,10 @@ Usage Notes
 * http://landfill.bugzilla.org/ for testing purposes -- opening test
 * bugs on production instances of Bugzilla is definitely not a good idea
 
-Run "bug-bugzilla --help" for a description of the possible options.
+Run "bugzilla-submit --help" for a description of the possible options.
 
 An example input file, named bugdata.txt, is provided. You can pipe it
-in as standard input to bug-bugzilla, providing a Bugzilla URI through
+in as standard input to bugzilla-submit, providing a Bugzilla URI through
 the command-line.
 
 Note that you must create a ~/.netrc entry to authenticate against the
@@ -41,6 +41,6 @@ your password password. An example entry follows:
 Documentation
 -------------
 
-Documentation for bug-bugzilla is provided in Docbook format; see
-bug-bugzilla.xml.
+Documentation for bugzilla-submit is provided in Docbook format; see
+bugzilla-submit.xml.
 
diff --git a/contrib/bugzilla-submit/bugzilla-submit b/contrib/bugzilla-submit/bugzilla-submit
index e16a968e7..0efa501fa 100755
--- a/contrib/bugzilla-submit/bugzilla-submit
+++ b/contrib/bugzilla-submit/bugzilla-submit
@@ -1,13 +1,13 @@
 #!/usr/bin/env python 
 #
-# bug-bugzilla: a command-line script to post bugs to a Bugzilla instance
+# bugzilla-submit: a command-line script to post bugs to a Bugzilla instance
 #
 # Authors: Christian Reis <kiko@async.com.br>
 #          Eric S. Raymond <esr@thyrsus.com>
 #
 # This is version 0.5.
 # 
-# For a usage hint run bug-bugzilla --help
+# For a usage hint run bugzilla-submit --help
 #
 # TODO: use RDF output to pick up valid options, as in
 #   http://www.async.com.br/~kiko/mybugzilla/config.cgi?ctype=rdf
@@ -15,7 +15,7 @@
 import sys
 
 def error(m):
-    sys.stderr.write("bug-bugzilla: %s\n" % m)
+    sys.stderr.write("bugzilla-submit: %s\n" % m)
     sys.stderr.flush()
     sys.exit(1)
 
diff --git a/contrib/bugzilla-submit/bugzilla-submit.xml b/contrib/bugzilla-submit/bugzilla-submit.xml
index da8a34c77..01ad49e63 100644
--- a/contrib/bugzilla-submit/bugzilla-submit.xml
+++ b/contrib/bugzilla-submit/bugzilla-submit.xml
@@ -2,20 +2,20 @@
 <!DOCTYPE refentry PUBLIC 
    "-//OASIS//DTD DocBook XML V4.1.2//EN"
    "docbook/docbookx.dtd">
-<refentry id='bug-bugzilla.1'>
+<refentry id='bugzilla-submit.1'>
 <refmeta>
-<refentrytitle>bug-bugzilla</refentrytitle>
+<refentrytitle>bugzilla-submit</refentrytitle>
 <manvolnum>1</manvolnum>
 <refmiscinfo class='date'>Oct 30, 2003</refmiscinfo>
 </refmeta>
 <refnamediv id='name'>
-<refname>bug-bugzilla</refname>
+<refname>bugzilla-submit</refname>
 <refpurpose>post bugs to a Bugzilla instance</refpurpose>
 </refnamediv>
 <refsynopsisdiv id='synopsis'>
 
 <cmdsynopsis>
-  <command>bug-bugzilla</command>
+  <command>bugzilla-submit</command>
   <arg choice='opt'>--status <replaceable>bug_status</replaceable></arg>
   <arg choice='opt'>--url <replaceable>bug_file_loc</replaceable></arg>
   <arg choice='opt'>--product <replaceable>product</replaceable></arg>
@@ -40,12 +40,12 @@
 
 <refsect1 id='description'><title>DESCRIPTION</title>
 
-<para><application>bug-bugzilla</application> is a command-line tool
+<para><application>bugzilla-submit</application> is a command-line tool
 for posting bug reports to any instance of Bugzilla.  It accepts on
 standard input text resembling an RFC-822 message.  The headers of
 that message, and its body, are used to set error-report field values.
 More field values are merged in from command-line options. If required
-fields have not been set, <application>bug-bugzilla</application>
+fields have not been set, <application>bugzilla-submit</application>
 tries to compute them.  Finally, the resulting error report is
 validated.  If all required fields are present, and there are no
 illegal fields or values, the report is shipped off to the Mozilla