summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorderaadt <deraadt@openbsd.org>2003-01-20 19:52:36 +0000
committerderaadt <deraadt@openbsd.org>2003-01-20 19:52:36 +0000
commit8813e63a4dfa065c09a895e9055ee77f28bf50de (patch)
treee6176381d102c4582947f7149ebd7d2e2fb72e77
parentuse LOG_NDELAY in chroot() using daemons (diff)
downloadwireguard-openbsd-8813e63a4dfa065c09a895e9055ee77f28bf50de.tar.xz
wireguard-openbsd-8813e63a4dfa065c09a895e9055ee77f28bf50de.zip
typos; alan@alanday.com
-rw-r--r--libexec/spamd/spamd.86
-rw-r--r--sbin/isakmpd/isakmpd.policy.510
-rw-r--r--usr.sbin/httpd/src/support/dbmmanage.18
3 files changed, 12 insertions, 12 deletions
diff --git a/libexec/spamd/spamd.8 b/libexec/spamd/spamd.8
index 745b6cebb1e..e9a37ac1c89 100644
--- a/libexec/spamd/spamd.8
+++ b/libexec/spamd/spamd.8
@@ -1,4 +1,4 @@
-.\" $OpenBSD: spamd.8,v 1.7 2003/01/01 21:04:56 deraadt Exp $
+.\" $OpenBSD: spamd.8,v 1.8 2003/01/20 19:52:51 deraadt Exp $
.\"
.\" Copyright (c) 2002 Theo de Raadt. All rights reserved.
.\"
@@ -75,7 +75,7 @@ The SMTP version banner that is reported upon initial connection.
is designed to be very efficient so that it does not slow down the
receiving machine. SPAM is never accepted, but always rejected with
either a 450 or 550 error message. The normal way that SPAM has been
-dealt with in the way is to either accept and drop, or outright block.
+dealt with in the past is to either accept and drop, or outright block.
When configured to use 450 responses,
.Nm
takes neither of these actions: it rejects the mail back to the senders'
@@ -86,7 +86,7 @@ is best started from
.Xr rc 8
and is used in conjuction with
.Xr spamd-setup 8
-which processes a list of spammers addresses, and applies appropriate
+which processes a list of spammers' addresses, and applies appropriate
.Xr pfctl 8
rdr rules.
.Pp
diff --git a/sbin/isakmpd/isakmpd.policy.5 b/sbin/isakmpd/isakmpd.policy.5
index ef32647f330..1b97bdc0cd0 100644
--- a/sbin/isakmpd/isakmpd.policy.5
+++ b/sbin/isakmpd/isakmpd.policy.5
@@ -1,4 +1,4 @@
-.\" $OpenBSD: isakmpd.policy.5,v 1.28 2003/01/19 21:02:15 deraadt Exp $
+.\" $OpenBSD: isakmpd.policy.5,v 1.29 2003/01/20 19:52:36 deraadt Exp $
.\" $EOM: isakmpd.policy.5,v 1.24 2000/11/23 12:55:25 niklas Exp $
.\"
.\" Copyright (c) 1999-2001, Angelos D. Keromytis. All rights reserved.
@@ -58,7 +58,7 @@ authenticating each other and establishing key material for
encrypting/authenticating future communications between them.
This step is typically only performed once for every pair of IKE daemons.
.Pp
-In the second stage (also called Quick Mode), the two IKE daemon
+In the second stage (also called Quick Mode), the two IKE daemons
create the pair of SAs for the parties that wish to communicate using
IPsec.
These parties may be the hosts the IKE daemons run on, a host
@@ -68,7 +68,7 @@ At this stage, the exact parameters of the SAs
(e.g., algorithms to use, encapsulation mode, lifetime) and the
identities of the communicating parties (hosts, networks, etc.) are
specified.
-The reason for the existance of Quick Mode is to allow for fast
+The reason for the existence of Quick Mode is to allow for fast
SA setup, once the more heavy-weight Main Mode has been completed.
Generally, Quick Mode uses the key material derived from Main Mode to
provide keys to the IPsec transforms to be used.
@@ -212,7 +212,7 @@ on how to specify what credentials to send in an IKE exchange.
Passphrases that appear in the Licensees field are encoded as the
string "passphrase:", followed by the passphrase itself
(case-sensitive).
-Alternately (and preferably), they may be encoded using the
+Alternatively (and preferably), they may be encoded using the
"passphrase-md5-hex:" or "passphrase-sha1-hex:" prefixes, followed
by the
.Xr md5 1
@@ -261,7 +261,7 @@ non-existent attributes without catastrophic failures (access may be
denied, depending on the overall structure, but will not be
accidentally granted).
One reason for credentials referencing
-non-existant attributes is that they were defined within a specific
+non-existent attributes is that they were defined within a specific
implementation or network only.
.Pp
In the following attribute set, IPv4 addresses are encoded as ASCII
diff --git a/usr.sbin/httpd/src/support/dbmmanage.1 b/usr.sbin/httpd/src/support/dbmmanage.1
index 6c861e9364f..401bc3fa689 100644
--- a/usr.sbin/httpd/src/support/dbmmanage.1
+++ b/usr.sbin/httpd/src/support/dbmmanage.1
@@ -114,7 +114,7 @@ Deletes the \fIusername\fP entry from \fIfilename\fP.
.TP 12
.B import
Reads username:password entries (one per line) from STDIN and adds them to
-\fIfilename\fP. The passwords already has to be crypted.
+\fIfilename\fP. The password already has to be crypted.
.TP 12
.B update
Same as the "adduser" command, except that it makes sure \fIusername\fP
@@ -128,7 +128,7 @@ The user for which the update operation is performed.
.SH BUGS
.PP
One should be aware that there are a number of different DBM file
-formats in existance, and with all likelihood, libraries for more than
+formats in existence, and with all likelihood, libraries for more than
one format may exist on your system. The three primary examples are
NDBM, the GNU project's GDBM, and Berkeley DB 2. Unfortunately, all
these libraries use different file formats, and you must make sure
@@ -140,7 +140,7 @@ expects to see.
.B dbmmanage
currently has no way of determining what type of DBM file it is
looking at. If used against the wrong format,
-.dbmmanage
+.B dbmmanage
will simply return nothing, or may create a different DBM file with a
different name, or at worst, it may corrupt the DBM file if you were
attempting to write to it.
@@ -165,7 +165,7 @@ access these files.
.PP
Apache's
.B mod_auth_db.c
-module corresponds to Berkeley DB 2 library, while
+module corresponds to the Berkeley DB 2 library, while
.B mod_auth_dbm.c
corresponds to the NDBM library. Also, one can usually use the
.B file