X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=developer-duties.dbk;h=5b7f73d5501be4cf0aa9c9afa419373e2a6c8a99;hp=2e501f3069cf876bdabd480c891b0531dedc99c9;hb=430f868ef5cabbf6539d3051966de888d14277be;hpb=e3cb6d3f6afc7f8ed94ea6021aa0f9b4fa0e5551

diff --git a/developer-duties.dbk b/developer-duties.dbk
index 2e501f3..5b7f73d 100644
--- a/developer-duties.dbk
+++ b/developer-duties.dbk
@@ -160,8 +160,8 @@ upstream sources.
 Generally you should deal with bug reports on your packages as described in
 <xref linkend="bug-handling"/> .  However, there's a special category of bugs
 that you need to take care of — the so-called release-critical bugs (RC
-bugs).  All bug reports that have severity <emphasis>critical</emphasis>,
-<emphasis>grave</emphasis> or <emphasis>serious</emphasis> are considered to
+bugs).  All bug reports that have severity <literal>critical</literal>,
+<literal>grave</literal> or <literal>serious</literal> are considered to
 have an impact on whether the package can be released in the next stable
 release of Debian.  These bugs can delay the Debian release and/or can justify
 the removal of a package at freeze time.  That's why these bugs need to be