| 1 | fix documentation typos |
|---|
| 2 | |
|---|
| 3 | --- a/chat/chat.8 |
|---|
| 4 | +++ b/chat/chat.8 |
|---|
| 5 | @@ -51,7 +51,7 @@ keyword. When echoing is enabled, all ou |
|---|
| 6 | to \fIstderr\fR. |
|---|
| 7 | .TP |
|---|
| 8 | .B \-E |
|---|
| 9 | -Enables environment variable substituion within chat scripts using the |
|---|
| 10 | +Enables environment variable substitution within chat scripts using the |
|---|
| 11 | standard \fI$xxx\fR syntax. |
|---|
| 12 | .TP |
|---|
| 13 | .B \-v |
|---|
| 14 | @@ -78,7 +78,7 @@ SYSLOG. The use of \-S will prevent bot |
|---|
| 15 | error messages from being sent to the SYSLOG. |
|---|
| 16 | .TP |
|---|
| 17 | .B \-T \fI<phone number> |
|---|
| 18 | -Pass in an arbitary string, usually a phone number, that will be |
|---|
| 19 | +Pass in an arbitrary string, usually a phone number, that will be |
|---|
| 20 | substituted for the \\T substitution metacharacter in a send string. |
|---|
| 21 | .TP |
|---|
| 22 | .B \-U \fI<phone number 2> |
|---|
| 23 | @@ -205,7 +205,7 @@ terminal), standard error will normally |
|---|
| 24 | .LP |
|---|
| 25 | \fBSAY\fR strings must be enclosed in single or double quotes. If |
|---|
| 26 | carriage return and line feed are needed in the string to be output, |
|---|
| 27 | -you must explicitely add them to your string. |
|---|
| 28 | +you must explicitly add them to your string. |
|---|
| 29 | .LP |
|---|
| 30 | The SAY strings could be used to give progress messages in sections of |
|---|
| 31 | the script where you want to have 'ECHO OFF' but still let the user |
|---|
| 32 | @@ -458,7 +458,7 @@ For example, the character DC1 (17) is s |
|---|
| 33 | Environment variables are available within chat scripts, if the \fI\-E\fR |
|---|
| 34 | option was specified in the command line. The metacharacter \fI$\fR is used |
|---|
| 35 | to introduce the name of the environment variable to substitute. If the |
|---|
| 36 | -substition fails, because the requested environment variable is not set, |
|---|
| 37 | +substitution fails, because the requested environment variable is not set, |
|---|
| 38 | \fInothing\fR is replaced for the variable. |
|---|
| 39 | .SH TERMINATION CODES |
|---|
| 40 | The \fIchat\fR program will terminate with the following completion |
|---|
| 41 | --- a/pppd/pppd.8 |
|---|
| 42 | +++ b/pppd/pppd.8 |
|---|
| 43 | @@ -328,7 +328,7 @@ When this is completed, pppd will commen |
|---|
| 44 | The \fIdemand\fR option implies the \fIpersist\fR option. If this |
|---|
| 45 | behaviour is not desired, use the \fInopersist\fR option after the |
|---|
| 46 | \fIdemand\fR option. The \fIidle\fR and \fIholdoff\fR |
|---|
| 47 | -options are also useful in conjuction with the \fIdemand\fR option. |
|---|
| 48 | +options are also useful in conjunction with the \fIdemand\fR option. |
|---|
| 49 | .TP |
|---|
| 50 | .B domain \fId |
|---|
| 51 | Append the domain name \fId\fR to the local host name for authentication |
|---|
| 52 | @@ -929,7 +929,7 @@ pseudo-tty master/slave pair and use the |
|---|
| 53 | device. The \fIscript\fR will be run in a child process with the |
|---|
| 54 | pseudo-tty master as its standard input and output. An explicit |
|---|
| 55 | device name may not be given if this option is used. (Note: if the |
|---|
| 56 | -\fIrecord\fR option is used in conjuction with the \fIpty\fR option, |
|---|
| 57 | +\fIrecord\fR option is used in conjunction with the \fIpty\fR option, |
|---|
| 58 | the child process will have pipes on its standard input and output.) |
|---|
| 59 | .TP |
|---|
| 60 | .B receive\-all |
|---|
| 61 | @@ -1037,7 +1037,7 @@ in the pseudonym. |
|---|
| 62 | .TP |
|---|
| 63 | .B srp\-use\-pseudonym |
|---|
| 64 | When operating as an EAP SRP\-SHA1 client, attempt to use the pseudonym |
|---|
| 65 | -stored in ~/.ppp_psuedonym first as the identity, and save in this |
|---|
| 66 | +stored in ~/.ppp_pseudonym first as the identity, and save in this |
|---|
| 67 | file any pseudonym offered by the peer during authentication. |
|---|
| 68 | .TP |
|---|
| 69 | .B sync |
|---|
| 70 | --- a/README.pppoe |
|---|
| 71 | +++ b/README.pppoe |
|---|
| 72 | @@ -32,7 +32,7 @@ received from the PPPoE layer just as if |
|---|
| 73 | |
|---|
| 74 | With this in mind, the goal of the implementation of PPPoE support in |
|---|
| 75 | Linux is to allow users to simply specify that the device they intend |
|---|
| 76 | -to use for the PPP connection is an ethernet device (i.e. "eth0") and |
|---|
| 77 | +to use for the PPP connection is an ethernet device (e.g. "eth0") and |
|---|
| 78 | the rest of the system should function as usual. |
|---|
| 79 | |
|---|
| 80 | 2. Using PPPoE |
|---|