-<em/notified/ but not actually <em/closed/ by the non-maintainer.
-Technically, only the official package maintainer or the original bug
-submitter are allowed to close bugs. However, the person making the
-non-maintainer release must send a short message to the relevant bugs
-explaining that the bugs have been
-fixed by the NMU. Using <email/control@bugs.debian.org/, the party
-doing the NMU should also set the severity of the bugs fixed in the
-NMU to `fixed'. This ensures that everyone knows that the bug was
-fixed in an NMU; however the bug is left open until the changes in the
-NMU are incorporated officially into the package by the official
-package maintainer. Also, open a bug with the patches needed to
-fix the problem, or make sure that one of the other (already open) bugs
-has the patches.
+<em>notified</em> but not actually <em>closed</em> by the
+non-maintainer. Technically, only the official package maintainer or
+the original bug submitter are allowed to close bugs. However, the
+person making the non-maintainer release must send a short message to
+the relevant bugs explaining that the bugs have been fixed by the NMU.
+Using <email>control@bugs.debian.org</email>, the party doing the NMU
+should also set the severity of the bugs fixed in the NMU to `fixed'.
+This ensures that everyone knows that the bug was fixed in an NMU;
+however the bug is left open until the changes in the NMU are
+incorporated officially into the package by the official package
+maintainer. Also, open a bug with the patches needed to fix the
+problem, or make sure that one of the other (already open) bugs has
+the patches.