Hmm, the blog thing doesn't put author anywhere into the article

[mirror/dsa-wiki.git] / input / dsablog / 2010 / 02 / Securing_the_Debian_zones.mdwn

diff --git a/input/dsablog/2010/02/Securing_the_Debian_zones.mdwn b/input/dsablog/2010/02/Securing_the_Debian_zones.mdwn
index 2e93771..74d1b3d 100644 (file)
--- a/input/dsablog/2010/02/Securing_the_Debian_zones.mdwn
+++ b/input/dsablog/2010/02/Securing_the_Debian_zones.mdwn
@@ -11,7 +11,7 @@ to issues that arise without breaking everything at once.
 
 We will start with serving signed <code>debian.net</code> and
 <code>debian.com</code> zones.  Assuming nobody complains loudly enough
-the various reverse zones and finally the <code>debian.org</code> will
+the various reverse zones and finally the <code>debian.org</code> zone will
 follow.  Once all our zones are signed we will publish our trust anchors
 in [ISC's DLV Registry](https://www.isc.org/solutions/dlv), again in
 stages.
@@ -56,14 +56,16 @@ we can just put proper
 in the respective parent zone.
 
 Until we announce the first set of trust anchors on the mailinglist the
-keysets present in DNS should not be considered productional.  They can
+keysets present in DNS should be considered experimental.  They can
 be changed at any time, without observing standard rollover practices.
 
+Please direct questions or comments to either the debian-admin or, if
+you want a more public forum, the debian-project list at
+lists.debian.org.
+
 See also:
 
 * [DNSSEC wikipedia page](http://en.wikipedia.org/wiki/Domain_Name_System_Security_Extensions),
 * [DNSSEC HOWTO, a tutorial in disguise (Olaf Kolkman, nlnetlabs)](http://www.nlnetlabs.nl/publications/dnssec_howto/index.html).
 
-Please direct questions or comments to either the debian-admin or, if
-you want a more public forum, the debian-project list at
-lists.debian.org.
+-- Peter Palfrader