From 4af8cf98a07efa80e28c10020eb3e613e70283b0 Mon Sep 17 00:00:00 2001
From: Joseph Koshy <jkoshy@FreeBSD.org>
Date: Mon, 2 Nov 1998 03:20:46 +0000
Subject: [PATCH] Spelling fixes and typos.

Submitted by: PA <PA@FreeBSD.ee.ntu.edu.tw> via wosch@freebsd.org to the
	freebsd-doc list.
---
 FAQ/misc.sgml | 18 +++++++++---------
 1 file changed, 9 insertions(+), 9 deletions(-)

diff --git a/FAQ/misc.sgml b/FAQ/misc.sgml
index b29ff96e61..0a92dbbcb8 100644
--- a/FAQ/misc.sgml
+++ b/FAQ/misc.sgml
@@ -1,4 +1,4 @@
-<!-- $Id: misc.sgml,v 1.7 1998-10-08 00:23:37 imp Exp $ -->
+<!-- $Id: misc.sgml,v 1.8 1998-11-02 03:20:46 jkoshy Exp $ -->
 <!-- The FreeBSD Documentation Project -->
 
   <sect>
@@ -82,7 +82,7 @@
       library mechanism is based more closely on Sun's
       <tt>SunOS</tt>-style shared library mechanism and, as such, is very
       easy to use.  
-	  However, starting with 3.0, FreeBSD offically supports <tt/ELF/
+	  However, starting with 3.0, FreeBSD officially supports <tt/ELF/
 	  binaries as the default format.  Even though the <tt/a.out/
 	  executable format has served us well, the GNU people, who author the
 	  compiler tools we use, have dropped support for the <tt/a.out/
@@ -99,16 +99,16 @@
       <p>Back in the dim, dark past, there was simple hardware.  This
       simple hardware supported a simple, small system.  a.out was
       completely adequate for the job of representing binaries on this
-      simple system (a pdp-11).  As people ported unix from this
+      simple system (a PDP-11).  As people ported unix from this
       simple system, they retained the a.out format because it was
-      sufficent for the early ports of unix to thinks like the
-      motorola 68k, VAXen, etc.
+      sufficient for the early ports of unix to architectures like the
+      Motorola 68k, VAXen, etc.
 
-      <p>Then some bright hardware engineer desided that if he could
-      force software to do some sleezey tricks, then he'd be able to
-      shave a few gates off the design and allow his cpu core to run
+      <p>Then some bright hardware engineer decided that if he could
+      force software to do some sleazy tricks, then he'd be able to
+      shave a few gates off the design and allow his CPU core to run
       faster.  While it was made to work with this new kind of
-      hardware (known these dayss as RISC), <tt/a.out/ was ill-suited
+      hardware (known these days as RISC), <tt/a.out/ was ill-suited
       for this hardware, so many formats were developed to get to a
       better performance from this hardware than the limited, simple
       <tt/a.out/ format could offer.  Things like <tt/COFF/,