Fix typo: wierd -> weird.

There is no such thing as wierd in the english language.

libexec/telnetd/telnetd.c

@@ -110,7 +110,7 @@ int	registerd_host_only = 0;
 
 /*
  * Because of the way ptyibuf is used with streams messages, we need
- * ptyibuf+1 to be on a full-word boundary.  The following wierdness
+ * ptyibuf+1 to be on a full-word boundary.  The following weirdness
  * is simply to make that happen.
  */
 long	ptyibufbuf[BUFSIZ/sizeof(long)+1];

sys/compat/svr4/svr4_stream.c

@@ -2172,7 +2172,7 @@ svr4_sys_getmsg(p, uap)
 		if (st->s_cmd == SVR4_TI_CONNECT_REQUEST) {
 		        struct read_args ra;
 
-			/* More wierdness:  Again, I can't find documentation
+			/* More weirdness:  Again, I can't find documentation
 			 * to back this up, but when a process does a generic
 			 * "getmsg()" call it seems that the command field is
 			 * zero and the length of the data area is zero.  I

sys/dev/cardbus/cardbus.c

@@ -79,7 +79,7 @@ static const char rcsid[] =
 struct cardbus_quirk {
 	u_int32_t devid;	/* Vendor/device of the card */
 	int	type;
-#define CARDBUS_QUIRK_MAP_REG	1 /* PCI map register in wierd place */
+#define CARDBUS_QUIRK_MAP_REG	1 /* PCI map register in weird place */
 	int	arg1;
 	int	arg2;
 };

sys/dev/ed/if_ed.c

@@ -3047,7 +3047,7 @@ ed_hpp_writemem(sc, src, dst, len)
  * Write to HP PC Lan+ NIC memory.  Access to the NIC can be by using 
  * outsw() or via the memory mapped interface to the same register.
  * Writes have to be in word units; byte accesses won't work and may cause
- * the NIC to behave wierdly. Long word accesses are permitted if the ASIC
+ * the NIC to behave weirdly. Long word accesses are permitted if the ASIC
  * allows it.
  */
 

sys/dev/isp/isp_target.c

@@ -87,7 +87,7 @@ static void isp_handle_ctio2(struct ispsoftc *, ct2_entry_t *);
  * The third group that can show up in the response queue are Immediate
  * Notification events. These include things like notifications of SCSI bus
  * resets, or Bus Device Reset messages or other messages received. This
- * a classic oddbins area. It can get  a little wierd because you then turn
+ * a classic oddbins area. It can get  a little weird because you then turn
  * around and acknowledge the Immediate Notify by writing an entry onto the
  * request queue and then the f/w turns around and gives you an acknowledgement
  * to *your* acknowledgement on the response queue (the idea being to let

sys/dev/pci/pci.c

@@ -151,7 +151,7 @@ static size_t	pci_vendordata_size;
 struct pci_quirk {
 	u_int32_t devid;	/* Vendor/device of the card */
 	int	type;
-#define PCI_QUIRK_MAP_REG	1 /* PCI map register in wierd place */
+#define PCI_QUIRK_MAP_REG	1 /* PCI map register in weird place */
 	int	arg1;
 	int	arg2;
 };

sys/kern/vfs_aio.c

@@ -2189,7 +2189,7 @@ lio_listio(struct proc *p, struct lio_listio_args *uap)
 
 #ifdef VFS_AIO
 /*
- * This is a wierd hack so that we can post a signal.  It is safe to do so from
+ * This is a weird hack so that we can post a signal.  It is safe to do so from
  * a timeout routine, but *not* from an interrupt routine.
  */
 static void

usr.bin/telnet/externs.h

@@ -39,7 +39,7 @@
 #endif
 
 /*
- * ucb stdio.h defines BSD as something wierd
+ * ucb stdio.h defines BSD as something weird
  */
 #if defined(sun) && defined(__svr4__)
 #define BSD 43