summaryrefslogtreecommitdiff
path: root/usr.sbin/dhcp/includes/cf/sample.h
diff options
context:
space:
mode:
Diffstat (limited to 'usr.sbin/dhcp/includes/cf/sample.h')
-rw-r--r--usr.sbin/dhcp/includes/cf/sample.h4
1 files changed, 2 insertions, 2 deletions
diff --git a/usr.sbin/dhcp/includes/cf/sample.h b/usr.sbin/dhcp/includes/cf/sample.h
index e50d8b17b0e..892303b977e 100644
--- a/usr.sbin/dhcp/includes/cf/sample.h
+++ b/usr.sbin/dhcp/includes/cf/sample.h
@@ -255,13 +255,13 @@ char *strerror PROTO ((int));
/* #define HAVE_SA_LEN */
-/* Every operating system has its own way of separating lines in a
+/* Every operating system has its own way of seperating lines in a
sequential text file. Most modern systems use a single character,
either an ASCII Newline (10) or an ASCII Carriage Return (13).
The most notable exception is MS-DOS (and consequently, Windows),
which uses an ASCII Carriage Return followed by a Newline to
- separate each line. Fortunately, MS-DOS C compiler libraries
+ seperate each line. Fortunately, MS-DOS C compiler libraries
typically hide this from the programmer, returning just a Newline.
Define EOL to be whatever getc() returns for a newline. */