- patch suggested by Debian lintian: allow to -> allow one to, from

  A. Schulze.

git-svn-id: file:///svn/unbound/trunk@4567 be551aaa-1e26-0410-a405-d3ace91eadb9

diff --git a/doc/Changelog b/doc/Changelog
index c6a6ba49495f4a04b64a42d9c6dcc856ea9af820..492a7637954bf15f55e008d957a70381a337c514 100644 (file)
--- a/doc/Changelog
+++ b/doc/Changelog
@@ -2,6 +2,8 @@
        - Fixed contrib/fastrpz.patch, even though this already applied
          cleanly for me, now also for others.
        - patch to log creates keytag queries, from A. Schulze.
+       - patch suggested by Debian lintian: allow to -> allow one to, from 
+         A. Schulze.
 
 6 March 2018: Wouter
        - Reverted fix for #3512, this may not be the best way forward;

diff --git a/doc/unbound.conf.5.in b/doc/unbound.conf.5.in
index f37477aa44f81b1330cbb19f2ad288f619acf3f1..90a9a9fa8effc9ea4bda97560b4809ad519ab3d0 100644 (file)
--- a/doc/unbound.conf.5.in
+++ b/doc/unbound.conf.5.in
@@ -1620,7 +1620,7 @@ but do not want to advertise over \fBdnscrypt\-provider\fR's TXT record certs
 distribution.
 A typical use case is when rotating certificates, existing clients may still use
 the client magic from the old cert in their queries until they fetch and update
-the new cert. Likewise, it would allow to prime the new cert/key without
+the new cert. Likewise, it would allow one to prime the new cert/key without
 distributing the new cert yet, this can be useful when using a network of
 servers using anycast and on which the configuration may not get updated at the
 exact same time. By priming the cert, the servers can handle both old and new