summaryrefslogtreecommitdiffstats
path: root/sbin/spppcontrol/spppcontrol.8
diff options
context:
space:
mode:
authorru <ru@FreeBSD.org>2005-02-13 22:25:33 +0000
committerru <ru@FreeBSD.org>2005-02-13 22:25:33 +0000
commit1541af42f12f8570fb332516efee8f1e030c3e46 (patch)
tree8a41fa7aceada1e7e82a06e67d6722b3c843f482 /sbin/spppcontrol/spppcontrol.8
parent13e88b41bac03367de7406f96648f28a64fc7322 (diff)
downloadFreeBSD-src-1541af42f12f8570fb332516efee8f1e030c3e46.zip
FreeBSD-src-1541af42f12f8570fb332516efee8f1e030c3e46.tar.gz
Expand *n't contractions.
Diffstat (limited to 'sbin/spppcontrol/spppcontrol.8')
-rw-r--r--sbin/spppcontrol/spppcontrol.84
1 files changed, 2 insertions, 2 deletions
diff --git a/sbin/spppcontrol/spppcontrol.8 b/sbin/spppcontrol/spppcontrol.8
index 0b038c2..a237936 100644
--- a/sbin/spppcontrol/spppcontrol.8
+++ b/sbin/spppcontrol/spppcontrol.8
@@ -141,7 +141,7 @@ For CHAP, this will be used to compute the response hash value, based
on remote's challenge.
For PAP, it will be transmitted as plain text
together with the system name.
-Don't forget to quote the secrets from
+Do not forget to quote the secrets from
the shell if they contain shell metacharacters (or white space).
.It Va myauthkey Ns Li = Ns Ar secret
Same as above.
@@ -170,7 +170,7 @@ Only meaningful with CHAP.
Do not re-challenge peer once the initial
CHAP handshake was successful.
Used to work around broken peer
-implementations that can't grok being re-challenged once the
+implementations that cannot grok being re-challenged once the
connection is up.
.It Ar rechallenge
With CHAP, send re-challenges at random intervals while the connection
OpenPOWER on IntegriCloud