From: Peter van Dijk <peter.van.dijk@netherlabs.nl>
Date: Fri, 10 Jan 2014 08:43:26 +0000 (+0100)
Subject: nit
X-Git-Tag: rec-3.6.0-rc1~253
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=9a27c9575e5a9c939f5c2f321f13541f7c29b1b2;p=thirdparty%2Fpdns.git

nit
---

diff --git a/pdns/docs/pdns.xml b/pdns/docs/pdns.xml
index 85e4ec8585..8113846ac2 100644
--- a/pdns/docs/pdns.xml
+++ b/pdns/docs/pdns.xml
@@ -13239,7 +13239,7 @@ $ pdnssec rectify-zone powerdnssec.org
 </section>
   <section id="dnssec-transfers"><title>Secure transfers</title>
   <para>
-    From 3.3.1. and up, PowerDNS support secure DNSSEC transfers as described in <ulink
+    From 3.3.1 and up, PowerDNS support secure DNSSEC transfers as described in <ulink
     url="https://ietf.org/doc/draft-koch-dnsop-dnssec-operator-change/">draft-koch-dnsop-dnssec-operator-change-05</ulink>.
     If the direct-dnskey option is enabled the foreign DNSKEY records stored in the database are added to the keyset and signed
     with the KSK. Without the direct-dnskey option DNSKEY records in the database are silently ignored.