seperate[d][ly] -> separate[d][ly]; alan@alanday.com

5 files changed, 6 insertions, 6 deletions

diff --git a/usr.sbin/dhcp/common/dhcp-options.5 b/usr.sbin/dhcp/common/dhcp-options.5
index 037bc53203c..6d2228d9731 100644
--- a/usr.sbin/dhcp/common/dhcp-options.5
+++ b/usr.sbin/dhcp/common/dhcp-options.5
@@ -100,7 +100,7 @@ The
 .B data-string
 data type specifies either an NVT ASCII string
 enclosed in double quotes, or a series of octets specified in
-hexadecimal, seperated by colons.   For example:
+hexadecimal, separated by colons.   For example:
 .nf
 .sp 1
 	option dhcp-client-identifier "CLIENT-FOO";
@@ -113,7 +113,7 @@ from the latest IETF draft document on DHCP options.   Options which
 are not listed by name may be defined by the name option-\fInnn\fR,
 where \fInnn\fI is the decimal number of the option code.   These
 options may be followed either by a string, enclosed in quotes, or by
-a series of octets, expressed as two-digit hexadecimal numbers seperated
+a series of octets, expressed as two-digit hexadecimal numbers separated
 by colons.   For example:
 .PP
 .nf
diff --git a/usr.sbin/dhcp/dhclient/dhclient-script.8 b/usr.sbin/dhcp/dhclient/dhclient-script.8
index 180fc2f05f5..dca93160ff8 100644
--- a/usr.sbin/dhcp/dhclient/dhclient-script.8
+++ b/usr.sbin/dhcp/dhclient/dhclient-script.8
@@ -104,7 +104,7 @@ When a binding has been completed, a lot of network parameters are
 likely to need to be set up.   A new /etc/resolv.conf needs to be
 created, using the values of $new_domain_name and
 $new_domain_name_servers (which may list more than one server,
-seperated by spaces).   A default route should be set using
+separated by spaces).   A default route should be set using
 $new_routers, and static routes may need to be set up using
 $new_static_routes.
 .PP
diff --git a/usr.sbin/dhcp/server/dhcpd.8 b/usr.sbin/dhcp/server/dhcpd.8
index 65b1d192ac8..32d73a55000 100644
--- a/usr.sbin/dhcp/server/dhcpd.8
+++ b/usr.sbin/dhcp/server/dhcpd.8
@@ -204,7 +204,7 @@ startup.   To avoid printing this message, the
 .B -q
 flag may be specified.
 .SH CONFIGURATION
-The syntax of the dhcpd.conf(5) file is discussed seperately.   This
+The syntax of the dhcpd.conf(5) file is discussed separately.   This
 section should be used as an overview of the configuration process,
 and the dhcpd.conf(5) documentation should be consulted for detailed
 reference information.
diff --git a/usr.sbin/dhcp/server/dhcpd.conf.5 b/usr.sbin/dhcp/server/dhcpd.conf.5
index b4b44ca8a62..aa63de67d1c 100644
--- a/usr.sbin/dhcp/server/dhcpd.conf.5
+++ b/usr.sbin/dhcp/server/dhcpd.conf.5
@@ -515,7 +515,7 @@ hardware type (and others) would also be desirable.
 The
 .I hardware-address
 should be a set of hexadecimal octets (numbers from 0 through ff)
-seperated by colons.   The \fIhardware\fR statement may also be used
+separated by colons.   The \fIhardware\fR statement may also be used
 for DHCP clients.
 .PP
 .B The
diff --git a/usr.sbin/dhcp/server/dhcpd.leases.5 b/usr.sbin/dhcp/server/dhcpd.leases.5
index b579c29d79e..a5bfef664ac 100644
--- a/usr.sbin/dhcp/server/dhcpd.leases.5
+++ b/usr.sbin/dhcp/server/dhcpd.leases.5
@@ -118,7 +118,7 @@ lease is recorded with the \fBhardware\fR statement:
  \fBhardware \fIhardware-type mac-address\fB;\fR
 .PP
 The MAC address is specified as a series of hexadecimal octets,
-seperated by colons.
+separated by colons.
 .PP
 If the client used a client identifier to acquire its address, the
 client identifier is recorded using the \fBuid\fR statement: