summaryrefslogtreecommitdiff
path: root/usr.sbin
diff options
context:
space:
mode:
authorTheo de Raadt <deraadt@cvs.openbsd.org>2002-05-30 06:23:14 +0000
committerTheo de Raadt <deraadt@cvs.openbsd.org>2002-05-30 06:23:14 +0000
commitd0cd675d6299c25f0981c730a0c243cf4bc79dc8 (patch)
tree9da1aa757ed2e7e0b8bd1ed78b62a265a1a784f3 /usr.sbin
parentf419afce84b48ef3ae02b9bbdb5d28e693300374 (diff)
typo; moritz@jodeit.org
Diffstat (limited to 'usr.sbin')
-rw-r--r--usr.sbin/dhcp/dhclient/dhclient.conf.52
1 files changed, 1 insertions, 1 deletions
diff --git a/usr.sbin/dhcp/dhclient/dhclient.conf.5 b/usr.sbin/dhcp/dhclient/dhclient.conf.5
index 691908193e0..76d5307bdfc 100644
--- a/usr.sbin/dhcp/dhclient/dhclient.conf.5
+++ b/usr.sbin/dhcp/dhclient/dhclient.conf.5
@@ -294,7 +294,7 @@ enforced - if you ignore it, the behaviour will be unpredictable.
\fBlease {\fR \fIlease-declaration\fR [ ... \fIlease-declaration ] \fB}\fR
.PP
The DHCP client may decide after some period of time (see \fBPROTOCOL
-TIMING\fR) decide that it is not going to succeed in contacting a
+TIMING\fR) that it is not going to succeed in contacting a
server. At that time, it consults its own database of old leases and
tests each one that has not yet timed out by pinging the listed router
for that lease to see if that lease could work. It is possible to