===================================================================
RCS file: /cvsrepo/anoncvs/cvs/www/report.html,v
retrieving revision 1.45
retrieving revision 1.46
diff -u -r1.45 -r1.46
--- www/report.html	2016/04/24 20:08:50	1.45
+++ www/report.html	2016/08/02 17:42:25	1.46
@@ -36,8 +36,8 @@
 
 <p>
 If nothing looks like it addresses your problem, then please become acquainted
-with <a href="http://man.openbsd.org/?query=sendbug">
-sendbug(1)</a> before submitting a bug report.
+with <a href="http://man.openbsd.org/sendbug">sendbug(1)</a> before submitting
+a bug report.
 
 <h3><font color="#0000e0">Current version problem reports</font></h3>
 
@@ -49,9 +49,9 @@
  <li>Do not report source tree compilation problems, unless they persist.
      They are almost always your mistake, or they are being worked on as you
      encounter them.
-     People working on the project are doing <a href="faq/faq5.html">
-     make build</a> at least once per day, and usually several times
-     per day with different architectures.
+     People working on the project are doing
+     <a href="faq/faq5.html">make build</a> at least once per day, and usually
+     several times per day with different architectures.
  <li>Remember that the <a href="anoncvs.html">AnonCVS</a> servers are
      updated a few hours behind the actual working source tree.
  <li>Check for <a href="plus.html">changes made between OpenBSD versions</a>
@@ -128,7 +128,7 @@
 <p>
  <li>A traceback from your kernel panic.
      If your kernel panicked and you are at a
-     <a href="http://man.openbsd.org/?query=ddb">ddb</a>
+     <a href="http://man.openbsd.org/ddb">ddb(4)</a>
      prompt, please provide the panic message, as well as the output of
      the <tt>trace</tt> and <tt>ps</tt> commands in your bug report as
      advised.
@@ -143,10 +143,9 @@
      The output of <tt>show registers</tt> might be of interest as well.
      You might then want to reboot with <tt>boot dump</tt> so that a kernel
      image could be saved by
-     <a href="http://man.openbsd.org/?query=savecore">
-     savecore(8)</a> for further post-mortem debugging, as described in the
-     <a href="http://man.openbsd.org/?query=crash">crash(8)</a>
-     man page.
+     <a href="http://man.openbsd.org/savecore">savecore(8)</a> for further
+     post-mortem debugging, as described in the
+     <a href="http://man.openbsd.org/crash">crash(8)</a> man page.
 <p>
    <li>If you're reporting a problem with the X Window System on an
    architecture that uses the X.Org server, please include the full 
@@ -162,11 +161,9 @@
 On the other hand, if your input files are huge, it is fair to ask first
 whether somebody is interested in looking into it.
 
-<a name="bugtypes"></a>
-<h3><font color="#0000e0">Sending in bug reports</font></h3>
+<h3 id="bugtypes"><font color="#0000e0">Sending in bug reports</font></h3>
 
-If possible, use the
-<a href="http://man.openbsd.org/?query=sendbug">sendbug(1)</a>
+If possible, use the <a href="http://man.openbsd.org/sendbug">sendbug(1)</a>
 command to help generate your bug report.
 It will automatically include some useful information about your hardware
 that helps diagnose many issues.