[src/trunk]: src/dist/dhcp/server Typo fix.

[wiz <wiz%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/b3b51fef3d98
branches:  trunk
changeset: 513555:b3b51fef3d98
user:      wiz <wiz%NetBSD.org@localhost>
date:      Fri Aug 03 13:50:07 2001 +0000

description:
Typo fix.

diffstat:

 dist/dhcp/server/dhcpd.conf.5 |  2 +-
 1 files changed, 1 insertions(+), 1 deletions(-)

diffs (12 lines):

diff -r d68cc78061fb -r b3b51fef3d98 dist/dhcp/server/dhcpd.conf.5
--- a/dist/dhcp/server/dhcpd.conf.5     Fri Aug 03 13:47:17 2001 +0000
+++ b/dist/dhcp/server/dhcpd.conf.5     Fri Aug 03 13:50:07 2001 +0000
@@ -1127,7 +1127,7 @@
 Note that the zone declarations have to correspond to authority
 records in your name server - in the above example, there must be an
 SOA record for "example.org." and for "17.10.10.in-addr.arpa.".   For
-example, if there were a subdoman "foo.example.org" with no separate
+example, if there were a subdomain "foo.example.org" with no separate
 SOA, you could not write a zone declaration for "foo.example.org."  
 Also keep in mind that zone names in your DHCP configuration should end in a
 "."; this is the preferred syntax.  If you do not end your zone name in a