diff options
| author |   jmc <jmc@openbsd.org> | 2007-09-24 19:56:34 +0000 |
|---|---|---|
| committer | jmc <jmc@openbsd.org> | 2007-09-24 19:56:34 +0000 |
| commit | 58ec2aaee007271929a47aa243b4b2cb3cb5e1c9 (patch) | |
| tree | 2bc0461bf0feb1e7d76cbe6f949576eee2c00512 | |
| parent | Add radio tap support. We still need to calculate correct RX rate and (diff) | |
| download | wireguard-openbsd-58ec2aaee007271929a47aa243b4b2cb3cb5e1c9.tar.xz wireguard-openbsd-58ec2aaee007271929a47aa243b4b2cb3cb5e1c9.zip | |
typos; from Pierre Riteau
| -rw-r--r-- | bin/ed/POSIX | 4 | ||||
| -rw-r--r-- | usr.bin/xlint/README | 4 |
2 files changed, 4 insertions, 4 deletions
diff --git a/bin/ed/POSIX b/bin/ed/POSIX index bb125f0c657..efa84715db3 100644 --- a/bin/ed/POSIX +++ b/bin/ed/POSIX @@ -1,4 +1,4 @@ -$OpenBSD: POSIX,v 1.3 1999/06/06 07:03:01 pjanzen Exp $ +$OpenBSD: POSIX,v 1.4 2007/09/24 19:56:34 jmc Exp $ $NetBSD: POSIX,v 1.9 1995/03/21 09:04:32 cgd Exp $ This version of ed(1) is not strictly POSIX compliant, as described in @@ -78,7 +78,7 @@ DEVIATIONS 2) Since the behavior of `u' (undo) within a `g' (global) command list is not specified by POSIX, it follows the behavior of the SunOS ed: undo forces a global command list to be executed only once, rather than - for each line matching a global pattern. In addtion, each instance of + for each line matching a global pattern. In addition, each instance of `u' within a global command undoes all previous commands (including undo's) in the command list. This seems the best way, since the alternatives are either too complicated to implement or too confusing diff --git a/usr.bin/xlint/README b/usr.bin/xlint/README index 31f9d5d65d4..0692d6f77c2 100644 --- a/usr.bin/xlint/README +++ b/usr.bin/xlint/README @@ -15,7 +15,7 @@ lint1 keeps a symbol table for the current context, which always includes global symbols for the current translation unit, as well as locals (inside a function definition). When it parses a function definition, it pushes a symbol table context onto the stack, and -then pops it off when it when the function definition ends. +then pops it off when the function definition ends. lint1 does the vast majority of its checks one expression at a time. It uses the symbol table (which contains types of symbols) and almost @@ -27,4 +27,4 @@ of enclosing control blocks (loops, switch statements, etc). When lint1 is finished parsing an expression, you will not see any more warnings regarding that expression. -$OpenBSD: README,v 1.1 2006/04/26 16:33:38 cloder Exp $ +$OpenBSD: README,v 1.2 2007/09/24 19:56:34 jmc Exp $ |