X-Git-Url: http://www.chiark.greenend.org.uk/ucgi/~ianmdlvl/git?p=developers-reference.git;a=blobdiff_plain;f=best-pkging-practices.dbk;h=08a425da6a71ab90514be5200136b5639d7acea5;hp=c436c6f6bc0aeafa0cf70df38fdffaf6b7adefa7;hb=c42d5ef4b193ae79b912626ff70f9d972847095d;hpb=deb6e9334b71b51950c02335fc511d48099dcfc0

diff --git a/best-pkging-practices.dbk b/best-pkging-practices.dbk
index c436c6f..08a425d 100644
--- a/best-pkging-practices.dbk
+++ b/best-pkging-practices.dbk
@@ -567,9 +567,9 @@ inserting the title of each different bug.
 <para>
 Important news about changes in a package can also be put in
 <filename>NEWS.Debian</filename> files.
-The news will be displayed by tools like apt-listchanges, before all the rest
+The news will be displayed by tools like <systemitem role="package">apt-listchanges</systemitem>, before all the rest
 of the changelogs.  This is the preferred means to let the user know about
-significant changes in a package.  It is better than using debconf notes since
+significant changes in a package.  It is better than using <systemitem role="package">debconf</systemitem> notes since
 it is less annoying and the user can go back and refer to the
 <filename>NEWS.Debian</filename> file after the install.  And it's better than listing
 major changes in <filename>README.Debian</filename>, since the user can easily