Various minor documentation improvements:

remove repeated words

fix: it's to its

some minor formatting added
	(this needs to be improved still, there is a mix
	of \fB Bold and \fI underline for same things)

spelling fixes

minor punctuation fixes (remove ...)

uppercase an acronym that is not a config item

(I didn't get this reviewed, these all are very minor or obvious.)

server/dhcpd.8

@@ -246,7 +246,7 @@ automatically before installing it.
 .BI \-T
 Test the lease file.  The server tests the lease file
 for correct syntax, but will not attempt to perform any network
-operations.  This can be used to test a new leaes file
+operations.  This can be used to test a new lease file
 automatically before installing it.
 .TP
 .BI \-tf \ tracefile
@@ -273,7 +273,7 @@ Print version number and exit.
 .I Modifying default file locations:
 The following options can be used to modify the locations 
 .B dhcpd
-uses for it's files.  Because of the importance of using the same
+uses for its files.  Because of the importance of using the same
 lease database at all times when running dhcpd in production, these
 options should be used \fBonly\fR for testing lease files or database
 files in a non-production environment.

server/dhcpd.conf.5

@@ -780,7 +780,7 @@ The Failover pool balance statements.
 This version of the DHCP Server evaluates pool balance on a schedule,
 rather than on demand as leases are allocated.  The latter approach
 proved to be slightly klunky when pool misbalanced reach total
-saturation...when any server ran out of leases to assign, it also lost
+saturation \(em when any server ran out of leases to assign, it also lost
 its ability to notice it had run dry.
 .PP
 In order to understand pool balance, some elements of its operation
@@ -1228,12 +1228,12 @@ IP address, it can update its own A record, assuming that the
 .PP
 If the server is configured not to allow client updates, or if the
 client doesn't want to do its own update, the server will simply
-choose a name for the client from either the fqdn option (if present)
+choose a name for the client from either the \fBfqdn\fR option (if present)
 or the hostname option (if present).  It will use its own
 domain name for the client, just as in the ad-hoc update scheme.
 It will then update both the A and PTR record, using the name that it
 chose for the client.  If the client sends a fully-qualified domain
-name in the fqdn option, the server uses only the leftmost part of the
+name in the \fBfqdn\fR option, the server uses only the leftmost part of the
 domain name - in the example above, "jschmoe" instead of
 "jschmoe.radish.org".
 .PP
@@ -2051,7 +2051,7 @@ The \fIddns-hostname\fR statement
 .B ddns-hostname \fIname\fB;\fR
 .PP
 The \fIname\fR parameter should be the hostname that will be used in
-setting up the client's A and PTR records.  If no ddns-hostname is
+setting up the client's A and PTR records.  If no \fIddns-hostname\fR is
 specified in scope, then the server will derive the hostname
 automatically, using an algorithm that varies for each of the
 different update methods.
@@ -2199,7 +2199,7 @@ set to \fBinterim\fR.  Forward updates are enabled by default.  If
 this statement is used to disable forward updates, the DHCP server
 will never attempt to update the client's A record, and will only ever
 attempt to update the client's PTR record if the client supplies an
-FQDN that should be placed in the PTR record using the fqdn option.
+FQDN that should be placed in the PTR record using the \fBfqdn\fR option.
 If forward updates are enabled, the DHCP server will still honor the
 setting of the \fBclient-updates\fR flag.
 .RE
@@ -2454,7 +2454,7 @@ This statement causes the DHCP server to listen for DHCP requests sent
 to the specified \fIaddress\fR, rather than requests sent to all addresses.
 Since serving directly attached DHCP clients implies that the server must
 respond to requests sent to the all-ones IP address, this option cannot be
-used if clients are on directly attached networks...it is only realistically
+used if clients are on directly attached networks; it is only realistically
 useful for a server whose only clients are reached via unicasts, such as via
 DHCP relay agents.
 .PP
@@ -2509,6 +2509,7 @@ Because the \fIlog-facility\fR setting is controlled by the dhcpd.conf
 file, log messages printed while parsing the dhcpd.conf file or before
 parsing it are logged to the default log facility.  To prevent this,
 see the README file included with this distribution, which describes
+BUG: where is that mentioned in README?
 how to change the default log facility.  When this parameter is used,
 the DHCP server prints its startup message a second time after parsing
 the configuration file, so that the log will be as complete as

server/dhcpd.leases.5

@@ -215,7 +215,7 @@ manual page.
 .B The \fIddns-text\fB variable
 .PP
 The \fIddns-text\fR variable is used to record the value of the
-client's TXT identification record when the interim ddns update
+client's TXT identification record when the interim DDNS update
 style has been used to update the DNS for a particular lease.
 .PP
 .B The \fIddns-fwd-name\fB variable
@@ -227,9 +227,9 @@ update the client's PTR record.
 .PP
 .B The \fIddns-client-fqdn\fB variable
 .PP
-If the server is configured to use the interim ddns update style, and
-is also configured to allow clients to update their own fqdns, and the
-client did in fact update its own fqdn, then the
+If the server is configured to use the interim DDNS update style, and
+is also configured to allow clients to update their own FQDNs, and the
+client did in fact update its own FQDN, then the
 \fIddns-client-fqdn\fR variable records the name that the client has
 indicated it is using.   This is the name that the server will have
 used to update the client's PTR record in this case.