From: Harlan Stenn <stenn@ntp.org>
Date: Sat, 3 Feb 2018 09:22:07 +0000 (-0800)
Subject: cleanup
X-Git-Url: http://git.ipfire.org/cgi-bin/gitweb.cgi?a=commitdiff_plain;h=7c73acfc77956737f7e7bfcee18d8268188d5d0c;p=thirdparty%2Fntp.git

cleanup

bk: 5a757f3fKeOzJ9AAJ7Sl72sfQIL-BQ
---

diff --git a/ntpd/ntp.conf.def b/ntpd/ntp.conf.def
index 1e70149ae..4af774216 100644
--- a/ntpd/ntp.conf.def
+++ b/ntpd/ntp.conf.def
@@ -2036,7 +2036,7 @@ there is clear benefit to having the clients notice this change
 as soon as possible.
 Attacks such as replay attacks can happen, however,
 and even though there are a number of protections built in to
-broadcast mode, attempts to perform  a replay attack are possible.
+broadcast mode, attempts to perform a replay attack are possible.
 This value defaults to 0, but can be changed
 to any number of poll intervals between 0 and 4.
 .El
@@ -2679,14 +2679,14 @@ The
 directive controls which network addresses
 .Xr ntpd 1ntpdmdoc
 opens, and whether input is dropped without processing.
-The first parameter determines the action  for addresses
+The first parameter determines the action for addresses
 which match the second parameter.
 The second parameter specifies a class of addresses,
 or a specific interface name,
 or an address.
 In the address case,
 .Ar prefixlen
-determines how many bits must match  for this rule to apply.
+determines how many bits must match for this rule to apply.
 .Cm ignore
 prevents opening matching addresses,
 .Cm drop