From: Wouter Wijngaards Date: Wed, 7 Mar 2018 08:40:09 +0000 (+0000) Subject: - patch suggested by Debian lintian: allow to -> allow one to, from X-Git-Tag: release-1.7.0rc2~4 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=babe659a643a3de7cb5bf087e36b6fa20143eb54;p=thirdparty%2Funbound.git - 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 c6a6ba494..492a76379 100644 --- 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 f37477aa4..90a9a9fa8 100644 --- 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