Typos: dbmmanage(1), isakmpd.policy(5)

From: Alan Day <alan(at)alanday.com>
Date: Mon Jan 20 2003 - 11:16:25 EST

Spelling and typos for isakmpd.policy(5) and dbmmanage(1)

existan[ce][t]->existen[ce][t]
alternately->alternatively

$ cd /usr/src
$ patch < /path/to/patch

Index: sbin/isakmpd/isakmpd.policy.5

---

RCS file: /cvs/src/sbin/isakmpd/isakmpd.policy.5,v retrieving revision 1.28
diff -u -r1.28 isakmpd.policy.5

--- sbin/isakmpd/isakmpd.policy.5	2003/01/19 21:02:15	1.28
+++ sbin/isakmpd/isakmpd.policy.5	2003/01/20 15:22:01

@@ -58,7 +58,7 @@
 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 @@
 (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 @@
 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 @@
 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 Index: usr.sbin/httpd/src/support/dbmmanage.1

---

RCS file: /cvs/src/usr.sbin/httpd/src/support/dbmmanage.1,v retrieving revision 1.6
diff -u -r1.6 dbmmanage.1

--- usr.sbin/httpd/src/support/dbmmanage.1	2002/12/07 15:39:33	1.6
+++ usr.sbin/httpd/src/support/dbmmanage.1	2003/01/20 15:22:01

@@ -114,7 +114,7 @@
.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 @@
.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 @@
.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 @@
.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
Received on Mon Jan 20 14:34:26 2003