Add a couple of code markers for tags and states

Otherwise when converting from markdown to the html page the tag
is used as html tag and not showing up on.

git-svn-id: svn+ssh://svn.debian.org/svn/secure-testing@54595 e39458fd-73e7-0310-bf30-c45bca0a0e42

1 files changed, 5 insertions, 5 deletions

diff --git a/doc/security-team.d.o/security_tracker b/doc/security-team.d.o/security_tracker
index 745b566496..d5d672e4df 100644
--- a/doc/security-team.d.o/security_tracker
+++ b/doc/security-team.d.o/security_tracker
@@ -211,7 +211,7 @@ If you want to report a bug, bin/report-vuln might be helpful in creating
 the bug report.
 
 If a vulnerability does not affect Debian, e.g., because the vulnerable
-code is not contained, it is marked as <not-affected>:
+code is not contained, it is marked as `<not-affected>`:
 
     CVE-2004-2628 (Multiple directory traversal vulnerabilities in thttpd 2.07 beta 0.4, ...)
             - thttpd <not-affected> (Windows-specific vulnerabilities)
@@ -224,7 +224,7 @@ package was uploaded into the Debian archive.
 
 If you don't have time to fully research an issue, but it is abundantly
 clear (via CVE text or other announcement) that the issue affects a
-particular package or set of packages, the <undetermined> tag can be
+particular package or set of packages, the `<undetermined>` tag can be
 used.  This has the advantage of entering the issue earlier in the
 output of debsecan and on the PTS pages, which is useful for the small
 set of proactive maintainers paying attention to these information
@@ -248,7 +248,7 @@ The list of all of currently undetermined issues is aggregated
 This is a good place for new contributors to get started since these
 are issues that can be pruned quickly for new information that may
 not have been known during the initial disclosure, and thus marked
-<unfixed> for further work or closed with a version number.  Please
+`<unfixed>` for further work or closed with a version number.  Please
 add notes if you do change an undetermined issue to unfixed (unless
 you're also fixing the issue in the process, which is of course the
 ideal way to help/contribute).
@@ -273,7 +273,7 @@ is appreciated though. For example:
 If an issue is discovered in a package that has an RFP or ITP already filed,
 then that is also noted in order to track the problem, and made sure it is
 resolved before the package enters the archive.  These issues are marked with
-the <itp> tag.  Note this includes both ITPs and RFPs since (from a security
+the `<itp>` tag.  Note this includes both ITPs and RFPs since (from a security
 tracking standpoint) there is no advantage in tracking them in separate ways.
 An example entry for an ITP/RFP package is:
 
@@ -352,7 +352,7 @@ are marked with a distribution tag, the `<no-dsa>` state and an explanation.
 
 Two sub-states exists: `<ignored>` and `<postponed>`.
 
-If an issue will further be ignored the <ignored> state is used.
+If an issue will further be ignored the `<ignored>` state is used.
 
 If an issue deserves an update via a security advisory, but it is not needed to
 release an advisory just because of this issue, rather than `<no-dsa>` the