[Secure-testing-commits] r8967 - doc

[nion at alioth.debian.org]

Author: nion
Date: 2008-06-04 10:47:05 +0000 (Wed, 04 Jun 2008)
New Revision: 8967

Modified:
   doc/bits_2008_06_x
Log:
fix brackets

Modified: doc/bits_2008_06_x
===================================================================
--- doc/bits_2008_06_x	2008-06-04 10:43:11 UTC (rev 8966)
+++ doc/bits_2008_06_x	2008-06-04 10:47:05 UTC (rev 8967)
@@ -25,7 +25,7 @@
 
 With some pride we can say that testing was never in such good shape before
 in regards to security. The tracker is reflecting known security issues in
-the testing distribution(0). The new announcement emails provide a notification
+the testing distribution[0]. The new announcement emails provide a notification
 for users, whenever a new security fix reaches testing, whether through
 migration from unstable or DTSA for testing-security. Also fewer packages are
 getting removed from testing, because of security issues. 
@@ -33,7 +33,7 @@
 In order to reach a wider audience with security updates for testing, a new mailinglist
 was created, called debian-testing-security-announce at lists.debian.org
 We highly recommend that every user, who runs Debian testing and is concerned 
-about security subscribed to the debian-testing-security announcement list(1).
+about security subscribed to the debian-testing-security announcement list[1].
 
 
 Security status of the next testing distribution (lenny+1):
@@ -61,11 +61,11 @@
 close contact with the Debian Testing Security Team to coordinate security
 updates for the testing distribution. If one of your packages is affected by
 an unembargoed security issue, please contact us through the public list of
-the team(2) and fix the issue in unstable with high urgency. Please send as
+the team[2] and fix the issue in unstable with high urgency. Please send as
 many information as possible, including patches, ways to reproduce the issue
 and further descriptions. If we ask you to prepare a DTSA, please follow the
-instructions on the testing-security webpage(3) and go ahead with the upload.
-If your package is affected by an embargoed issue, email the private list(4)
+instructions on the testing-security webpage[3] and go ahead with the upload.
+If your package is affected by an embargoed issue, email the private list[4]
 and if we should ask you to upload a DTSA, use the embargoed upload queue
 (which is the same than for stable/oldstable).
 
@@ -81,7 +81,7 @@
 unstable. For this purpose, we urge every maintainer to upload their security
 fixes with high urgency and mention the CVE ids (if given) in their changelogs.
 Because we let fixes migrate, it often happens that we NMU packages. An up to date
-list of NMUs done by the security team can be found in the svn(5). These NMUs
+list of NMUs done by the security team can be found in the svn[5]. These NMUs
 are done as the need arises and do not allways follow the given NMU rules, because
 security updates are treated with higher urgency. If you happen to get a bug
 reported against one of your packages, please speak up, but if a working patch is
@@ -93,9 +93,9 @@
 
 The team is still looking for new members. If you are interested in joining the
 Debian Testing Security Team, please speak up and either write to the public
-mailing list(6) or approach us under on the internal mailing list(6). Note that
+mailing list[6] or approach us under on the internal mailing list[6]. Note that
 you do not have to be a DD for all tasks. Your work would include to keep the
-security tracker(8) up to date, report bugs about new unembargoed issues to the
+security tracker[8] up to date, report bugs about new unembargoed issues to the
 BTS, give advice to maintainers and track the bugs, write and/or review patches,
 propose NMUs and take care of DTSAs. If you are interested, but unsure that you
 can cope with all this, we offer some level of mentoring for new members, where