diff --git a/doc/misc/migration b/doc/misc/migration
index a14d7e2a55..9284744218 100644
--- a/doc/misc/migration
+++ b/doc/misc/migration
@@ -38,7 +38,7 @@ do cause the zone not to load.
 1.3. Logging
 
 The set of logging categories in BIND 9 is different from that
-in BIND 8.  If you have customized your logging on a per-category
+in BIND 8.  If you have customised your logging on a per-category
 basis, you need to modify your logging statement to use the
 new categories.
 
@@ -50,7 +50,7 @@ server first starts up, regardless of the contents of the "logging"
 statement.  In BIND 8, the new logging configuration took effect
 immediately after the "logging" statement was read.
 
-1.4. Notify messages and Refesh queries
+1.4. Notify messages and Refresh queries
 
 The source address and port for these is now controlled by
 "notify-source" and "transfer-source", respectively, rather that
@@ -78,10 +78,10 @@ and use the value of the SOA MINTTL field as a default for missing TTL
 values.
 
 BIND 9.0 and 9.1 completely refused to load such files.  BIND 9.2
-emulates the nonstandard BIND 4/8 SOA MINTTL behavior and loads the
+emulates the nonstandard BIND 4/8 SOA MINTTL behaviour and loads the
 files anyway (provided the SOA is the first record in the file), but
 will issue the warning message "no TTL specified; using SOA MINTTL
-instad".
+instead".
 
 To avoid problems, we recommend that you use a $TTL directive in each
 zone file.
@@ -125,7 +125,7 @@ name is deprecated.  Use \$ instead.
 
 BIND 9 uses EDNS0 (RFC2671) to advertise its receive buffer size.  It
 also sets an EDNS flag bit in queries to indicate that it wishes to
-receive DNSSEC responses; this flag bit usage is not yet standardized,
+receive DNSSEC responses; this flag bit usage is not yet standardised,
 but we hope it will be.
 
 Most older servers that do not support EDNS0, including prior versions
@@ -219,11 +219,11 @@ records and would "leak" the child's NS records into the parent,
 effectively causing the parent zone to be silently modified: responses
 and zone transfers from the parent contained the child's NS records
 rather than the glue configured into the parent (if any).  In the case
-of children of type "stub", this behavior was documented as a feature,
+of children of type "stub", this behaviour was documented as a feature,
 allowing the glue NS records to be omitted from the parent
 configuration.
 
-Sites that were relying on this BIND 8 behavior need to add any
+Sites that were relying on this BIND 8 behaviour need to add any
 omitted glue NS records, and any necessary glue A records, to the
 parent zone.
 
@@ -243,4 +243,4 @@ necessary, the umask should be set explicitly in the script used to
 start the named process.
 
 
-$Id: migration,v 1.37.2.1 2001/09/21 17:49:58 gson Exp $
+$Id: migration,v 1.37.2.2 2003/04/22 04:30:06 marka Exp $