[fF]uther -> [fF]urther in comments and man page. First one spotted on

tech@ by Jung.

5 files changed, 11 insertions, 11 deletions

diff --git a/sys/arch/hppa/dev/sti_sgc.c b/sys/arch/hppa/dev/sti_sgc.c
index b6de6c152cd..bfe294bf753 100644
--- a/sys/arch/hppa/dev/sti_sgc.c
+++ b/sys/arch/hppa/dev/sti_sgc.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: sti_sgc.c,v 1.36 2007/08/23 19:13:28 kettenis Exp $	*/
+/*	$OpenBSD: sti_sgc.c,v 1.37 2007/09/15 14:28:17 krw Exp $	*/
 
 /*
  * Copyright (c) 2000-2003 Michael Shalayeff
@@ -117,7 +117,7 @@ sti_sgc_probe(parent, match, aux)
 	if (ca->ca_type.iodc_type != HPPA_TYPE_FIO)
 		return (0);
 
-	/* these need futher checking for the graphics id */
+	/* these need further checking for the graphics id */
 	if (ca->ca_type.iodc_sv_model != HPPA_FIO_GSGC &&
 	    ca->ca_type.iodc_sv_model != HPPA_FIO_SGC)
 		return 0;
diff --git a/sys/arch/powerpc/powerpc/pmap.c b/sys/arch/powerpc/powerpc/pmap.c
index dbfd7ab5c75..d303f6cd5f1 100644
--- a/sys/arch/powerpc/powerpc/pmap.c
+++ b/sys/arch/powerpc/powerpc/pmap.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: pmap.c,v 1.101 2007/05/27 15:46:02 drahn Exp $ */
+/*	$OpenBSD: pmap.c,v 1.102 2007/09/15 14:28:17 krw Exp $ */
 
 /*
  * Copyright (c) 2001, 2002, 2007 Dale Rahn.
@@ -369,7 +369,7 @@ PTED_VALID(struct pte_desc *pted)
  * it is likely that it will be mapped at some point, but would it also
  * make sense to use a tree/table like is use for pmap to store device
  * mappings?
- * Futher notes: It seems that the PV table is only used for pmap_protect
+ * Further notes: It seems that the PV table is only used for pmap_protect
  * and other paging related operations. Given this, it is not necessary
  * to store any pmap_kernel() entries in PV tables and does not make
  * sense to store device mappings in PV either.
diff --git a/sys/arch/vax/uba/qv.c b/sys/arch/vax/uba/qv.c
index fbf9371a67f..4ae41721a87 100644
--- a/sys/arch/vax/uba/qv.c
+++ b/sys/arch/vax/uba/qv.c
@@ -1,4 +1,4 @@
-/*	$OpenBSD: qv.c,v 1.12 2006/01/17 20:26:16 miod Exp $	*/
+/*	$OpenBSD: qv.c,v 1.13 2007/09/15 14:28:17 krw Exp $	*/
 /*	$NetBSD: qv.c,v 1.2 1996/09/02 06:44:28 mycroft Exp $	*/
 
 /*-
@@ -118,7 +118,7 @@
  *      As a further complication this driver is required to function as the
  *      virtual system console. This code runs before and during auto-
  *      configuration and therefore is require to have a second path for setup.
- *      It is futher constrained to have a character output routine that
+ *      It is further constrained to have a character output routine that
  *      is not dependant on the interrupt system.
  *
  */
diff --git a/usr.sbin/httpd/src/main/buff.c b/usr.sbin/httpd/src/main/buff.c
index b29fd3afe4b..bcd40b59e31 100644
--- a/usr.sbin/httpd/src/main/buff.c
+++ b/usr.sbin/httpd/src/main/buff.c
@@ -113,7 +113,7 @@
  * be done.
  *
  * On an error except for EAGAIN, ERROR will be set in the flags and no
- * futher I/O will be done
+ * further I/O will be done
  */
 
 
@@ -1072,7 +1072,7 @@ API_EXPORT(int) ap_bflush(BUFF *fb)
 /*
  * Flushes and closes the file, even if an error occurred.
  * Discards an data that was not read, or not written by bflush()
- * Sets the EOF flag to indicate no futher data can be read,
+ * Sets the EOF flag to indicate no further data can be read,
  * and the EOUT flag to indicate no further data can be written.
  */
 API_EXPORT(int) ap_bclose(BUFF *fb)
diff --git a/usr.sbin/ospfd/ospfd.8 b/usr.sbin/ospfd/ospfd.8
index e4be84e3c9a..2daa6180c0d 100644
--- a/usr.sbin/ospfd/ospfd.8
+++ b/usr.sbin/ospfd/ospfd.8
@@ -1,4 +1,4 @@
-.\"	$OpenBSD: ospfd.8,v 1.16 2007/09/12 09:40:19 jmc Exp $
+.\"	$OpenBSD: ospfd.8,v 1.17 2007/09/15 14:28:17 krw Exp $
 .\"
 .\" Copyright (c) 2004, 2005, 2007 Esben Norby <norby@openbsd.org>
 .\"
@@ -14,7 +14,7 @@
 .\" ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF
 .\" OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE.
 .\"
-.Dd $Mdocdate: September 12 2007 $
+.Dd $Mdocdate: September 15 2007 $
 .Dt OSPFD 8
 .Os
 .Sh NAME
@@ -50,7 +50,7 @@ omit the use of TCP and UDP.
 OSPF has several advantages over RIP.
 For example every router has a complete network topology.
 Response to changes in the network are faster.
-Futhermore fail detection is much improved.
+Furthermore fail detection is much improved.
 .Pp
 All routers in an OSPF network spend most of their time keeping each others
 LSDBs in sync.