-Send mail to
-<A href="mailto:submit\@$gEmailDomain"><code>submit\@$gEmailDomain</code></A>,
-as described below.
-<p>
-
-Please don't report several unrelated $gBugs - especially ones in
-different packages - in one message. Also, please don't mail your $gBug
-report to any mailing lists or recipients other than
-<code>submit\@$gEmailDomain</code> (for details of how to do this right, see
-<A href="#xcc">below</A>).
-<p>
-
-Lists of currently-outstanding $gBugs are available <A href="./">on
-the World Wide Web</A> and <A href="Access.html">elsewhere</A> - see
-other documents for details.
-<p>
-
-You should put a pseudo-header at the start of the body of the
-message, with the <code>Package:</code> and <code>Version:</code>
-lines giving the name and version of the package which has the $gBug.
-(The pseudo-header fields must start at the very start of their lines,
-and the $gBug system does not currently understand them if they're
-buried in MIMEd or PGPd mail.)
+<h2>Important things to note <strong>before</strong> sending</h2>
+
+<p>Please don't report multiple unrelated $gBugs - especially ones in
+different packages - in a single $gBug report. It makes our lives much
+easier if you send separate reports.
+
+<p>You should check if your $gBug report has already been filed by someone
+else before submitting it. Lists of currently outstanding $gBugs are
+available <a href="./">on the World Wide Web</a> and
+<a href="Access.html">elsewhere</a> - see other documents for details.
+You can submit your comments to an existing $gBug report
+#<var><number></var> by sending e-mail to
+<var><number></var>\@$gEmailDomain</p>
+
+<p>If you can't seem to determine which package contains the problem,
+please send e-mail to the <a href="mailto:$gMaintainerEmail">
+$gMaintainerEmail</a> asking for advice.
+$gHTMLPseudoDesc
+</p>
+
+<p>If you'd like to send a copy of your $gBug report to additional
+recipients (such as mailing lists), you shouldn't use the usual e-mail
+headers, but <a href="#xcc">a different method, described below</a>.</p>
+
+
+<h2>Sending the bug report using an automatic bug report tool</h2>
+
+<p>There is a program that was developed in Debian to help reporting
+$gBug reports, it's called
+<code><a href="http://packages.debian.org/stable/utils/reportbug">reportbug</a></code>.
+It will guide you through the bug reporting process step by step,
+and probably ease filing bugs that way.</p>
+
+<p>Emacs users can also use the debian-bug command provided by the
+<code><a href="http://packages.debian.org/stable/utils/debbugs-el">
+debbugs-el</a></code> package. When called with <kbd>M-x
+debian-bug</kbd>, it will ask for all necessary information in a
+similar way to <code>reportbug</code>.</p>
+
+
+<h2>Sending the bug report via e-mail</h2>
+
+<p>Send mail to
+<a href="mailto:submit\@$gEmailDomain"><code>submit\@$gEmailDomain</code></a>,
+as described below.</p>
+
+<p>Of course, like with any email, you should include a clear, descriptive
+<code>Subject</code> line in your main mail header. The subject you
+give will be used as the initial $gBug title in the tracking system, so
+please try to make it informative!</p>
+
+<p>You need to put a <a name="pseudoheader">pseudo-header</a> at the start
+of the body of the message. That means that the first line of the message
+body should say:</p>
+
+<pre>
+Package: <something>
+</pre>
+
+<p>Replace <code><something></code> with the name of the package which
+has the $gBug.</p>
+
+<p>The second line of the message should say:</p>
+
+<pre>
+Version: <something>
+</pre>
+
+<p>Replace <code><something></code> with the version of the package.
+Please don't include any text here other than the version itself, as the
+$gBug tracking system relies on this field to work out which releases are
+affected by the bug.</p>
+
+<p>You need to supply a correct <code>Package</code> line in the
+pseudo-header in order for the $gBug tracking system to deliver the message
+to the package's maintainer.</p>