Some small issues in the new section: - 'NTP servers' means actual servers, not the keyword, so remove the .Ic
- 'constraint' is used instead of 'constraint from' in some places; that might be ok as an abbreviation, but at least the example should use the full keyword. In the diff below, I used 'constraint from' everywhere. Index: usr.sbin/ntpd/ntpd.conf.5 =================================================================== RCS file: /cvs/src/usr.sbin/ntpd/ntpd.conf.5,v retrieving revision 1.27 diff -u -p -r1.27 ntpd.conf.5 --- usr.sbin/ntpd/ntpd.conf.5 10 Feb 2015 19:21:16 -0000 1.27 +++ usr.sbin/ntpd/ntpd.conf.5 14 Feb 2015 15:55:54 -0000 @@ -188,24 +188,23 @@ thereby reducing the impact of unauthent attacks. Received NTP packets with time information falling outside of a range near the constraint will be discarded and such NTP -.Ic servers -will be marked as invalid. +servers will be marked as invalid. .Bl -tag -width Ds .It Ic constraint from Ar url Specify the URL, IP address or the hostname of an HTTPS server to provide a constraint. If multiple -.Ic constraint +.Ic constraint from keywords are used, .Xr ntpd 8 will calculate a median constraint from all the servers specified. .Bd -literal -offset indent server ntp.example.org -constraint www.example.com +constraint from www.example.com .Ed .It Ic constraints from Ar url As with -.Ic constraint , +.Ic constraint from , specify the URL, IP address or the hostname of an HTTPS server to provide a constraint. Should the hostname resolve to multiple IP addresses,
