summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortb <tb@openbsd.org>2016-01-29 11:50:40 +0000
committertb <tb@openbsd.org>2016-01-29 11:50:40 +0000
commit7a3af63b2fc941cf1a07ee01ac8479d1e714e57d (patch)
tree1f1fc38dc96ce993d57b42a520d3f7465d70e2e2
parentSupport for RGB colour, using the extended cell mechanism to avoid (diff)
downloadwireguard-openbsd-7a3af63b2fc941cf1a07ee01ac8479d1e714e57d.tar.xz
wireguard-openbsd-7a3af63b2fc941cf1a07ee01ac8479d1e714e57d.zip
Therefor -> Therefore (where appropriate)
from ray@, ok jmc@
-rw-r--r--bin/ksh/NOTES4
-rw-r--r--lib/libssl/src/doc/apps/s_client.pod2
-rw-r--r--lib/libssl/src/doc/apps/s_time.pod2
-rw-r--r--sbin/growfs/growfs.c4
-rw-r--r--sys/uvm/uvm_pmemrange.c4
-rw-r--r--usr.bin/file/magdir/msdos4
6 files changed, 10 insertions, 10 deletions
diff --git a/bin/ksh/NOTES b/bin/ksh/NOTES
index 4cb0a129168..5fc1080bfbd 100644
--- a/bin/ksh/NOTES
+++ b/bin/ksh/NOTES
@@ -1,4 +1,4 @@
-$OpenBSD: NOTES,v 1.13 2015/12/06 17:18:42 mmcc Exp $
+$OpenBSD: NOTES,v 1.14 2016/01/29 11:50:40 tb Exp $
General features of at&t ksh88 that are not (yet) in pdksh:
- exported aliases and functions (not in ksh93).
@@ -180,7 +180,7 @@ Known differences between pdksh & at&t ksh (that are not likely to change)
(POSIX does not require the setting of variables to null so applications
shouldn't rely on this).
- in pdksh, ! substitution done before variable substitution; in at&t ksh
- it is done after substitution (and therefor may do ! substitutions on
+ it is done after substitution (and therefore may do ! substitutions on
the result of variable substitutions). POSIX doesn't say which is to be
done.
- pwd: in at&t ksh, it ignores arguments; in pdksh, it complains when given
diff --git a/lib/libssl/src/doc/apps/s_client.pod b/lib/libssl/src/doc/apps/s_client.pod
index 5e55c928b98..ea95414f3d2 100644
--- a/lib/libssl/src/doc/apps/s_client.pod
+++ b/lib/libssl/src/doc/apps/s_client.pod
@@ -282,7 +282,7 @@ for an appropriate page.
If a certificate is specified on the command line using the B<-cert>
option it will not be used unless the server specifically requests
-a client certificate. Therefor merely including a client certificate
+a client certificate. Therefore merely including a client certificate
on the command line is no guarantee that the certificate works.
If there are problems verifying a server certificate then the
diff --git a/lib/libssl/src/doc/apps/s_time.pod b/lib/libssl/src/doc/apps/s_time.pod
index 5a38aa2e039..5be91873d10 100644
--- a/lib/libssl/src/doc/apps/s_time.pod
+++ b/lib/libssl/src/doc/apps/s_time.pod
@@ -154,7 +154,7 @@ send an HTTP request for an appropriate page.
If a certificate is specified on the command line using the B<-cert>
option it will not be used unless the server specifically requests
-a client certificate. Therefor merely including a client certificate
+a client certificate. Therefore merely including a client certificate
on the command line is no guarantee that the certificate works.
=head1 BUGS
diff --git a/sbin/growfs/growfs.c b/sbin/growfs/growfs.c
index 96df2919a2a..4a8c506184c 100644
--- a/sbin/growfs/growfs.c
+++ b/sbin/growfs/growfs.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: growfs.c,v 1.48 2015/11/28 19:59:15 deraadt Exp $ */
+/* $OpenBSD: growfs.c,v 1.49 2016/01/29 11:50:40 tb Exp $ */
/*
* Copyright (c) 2000 Christoph Herrmann, Thomas-Henning von Kamptz
* Copyright (c) 1980, 1989, 1993 The Regents of the University of California.
@@ -300,7 +300,7 @@ growfs(int fsi, int fso, unsigned int Nflag)
*
* We probably should rather change the summary for the cylinder group
* statistics here to the value of what would be in there, if the file
- * system were created initially with the new size. Therefor we still
+ * system were created initially with the new size. Therefore we still
* need to find an easy way of calculating that.
* Possibly we can try to read the first superblock copy and apply the
* "diffed" stats between the old and new superblock by still copying
diff --git a/sys/uvm/uvm_pmemrange.c b/sys/uvm/uvm_pmemrange.c
index 001e249bad2..d7ae21f310a 100644
--- a/sys/uvm/uvm_pmemrange.c
+++ b/sys/uvm/uvm_pmemrange.c
@@ -1,4 +1,4 @@
-/* $OpenBSD: uvm_pmemrange.c,v 1.49 2015/12/06 10:42:43 blambert Exp $ */
+/* $OpenBSD: uvm_pmemrange.c,v 1.50 2016/01/29 11:50:40 tb Exp $ */
/*
* Copyright (c) 2009, 2010 Ariane van der Steldt <ariane@stack.nl>
@@ -192,7 +192,7 @@ uvm_pmemrange_addr_cmp(struct uvm_pmemrange *lhs, struct uvm_pmemrange *rhs)
* Comparator: sort by use ascending.
*
* The higher the use value of a range, the more devices need memory in
- * this range. Therefor allocate from the range with the lowest use first.
+ * this range. Therefore allocate from the range with the lowest use first.
*/
int
uvm_pmemrange_use_cmp(struct uvm_pmemrange *lhs, struct uvm_pmemrange *rhs)
diff --git a/usr.bin/file/magdir/msdos b/usr.bin/file/magdir/msdos
index 2a707af65c8..d71abee81bc 100644
--- a/usr.bin/file/magdir/msdos
+++ b/usr.bin/file/magdir/msdos
@@ -1,4 +1,4 @@
-# $OpenBSD: msdos,v 1.5 2009/04/24 18:54:34 chl Exp $
+# $OpenBSD: msdos,v 1.6 2016/01/29 11:50:40 tb Exp $
#------------------------------------------------------------------------------
# msdos: file(1) magic for MS-DOS files
@@ -650,7 +650,7 @@
#>0 string x , Magic: %s
# There are currently 2 Versions: "1" and "2"
-# I do not use Version 2 and therefor branch here
+# I do not use Version 2 and therefore branch here
# but can assure: it works (tested on both versions)
# Also my Qemu 0.9.0 which uses this Version 2 refuses
# to start in its bios