From 5de50b4d370d25cf01f739cbd98d2570eef442d0 Mon Sep 17 00:00:00 2001 From: billf Date: Sun, 30 May 1999 21:31:18 +0000 Subject: procedure, not proceedure. --- share/examples/ppp/ppp.conf.sample | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'share/examples/ppp') diff --git a/share/examples/ppp/ppp.conf.sample b/share/examples/ppp/ppp.conf.sample index 310a413..c89f6ea 100644 --- a/share/examples/ppp/ppp.conf.sample +++ b/share/examples/ppp/ppp.conf.sample @@ -4,7 +4,7 @@ # # Originally written by Toshiharu OHNO # -# $Id: ppp.conf.sample,v 1.3 1999/03/28 00:22:44 brian Exp $ +# $Id: ppp.conf.sample,v 1.4 1999/04/27 00:25:22 brian Exp $ # ################################################################# @@ -36,7 +36,7 @@ default: # Although the PPP protocol is a peer to peer protocol, we normally # consider the side that initiates the connection as the client and # the side that receives the connection as the server. Authentication -# is required by the server either using a unix-style login proceedure +# is required by the server either using a unix-style login procedure # or by demanding PAP or CHAP authentication from the client. # @@ -81,7 +81,7 @@ pmdemand: enable dns # If you want to use PAP or CHAP instead of using a unix-style login -# proceedure, do the following. Note, the peer suggests whether we +# procedure, do the following. Note, the peer suggests whether we # should send PAP or CHAP. By default, we send whatever we're asked for. # # You *MUST* customise ``MyName'' and ``MyKey'' below. -- cgit v1.1