update Y2K comment

diff --git a/doc/arm/Bv9ARM-book.xml b/doc/arm/Bv9ARM-book.xml
index 1a3fe018b7ac193a916dcb5d081b58fc7d6385b7..c92be5254cf152f817d2622e9abec557b0db453f 100644 (file)
--- a/doc/arm/Bv9ARM-book.xml
+++ b/doc/arm/Bv9ARM-book.xml
@@ -18,7 +18,7 @@
  - PERFORMANCE OF THIS SOFTWARE.
 -->
 
-<!-- File: $Id: Bv9ARM-book.xml,v 1.318 2007/04/24 01:54:36 marka Exp $ -->
+<!-- File: $Id: Bv9ARM-book.xml,v 1.319 2007/04/26 06:14:26 marka Exp $ -->
 <book xmlns:xi="http://www.w3.org/2001/XInclude">
   <title>BIND 9 Administrator Reference Manual</title>
 
@@ -10923,12 +10923,12 @@ zone "example.com" {
         <title>Incrementing and Changing the Serial Number</title>
 
         <para>
-          Zone serial numbers are just numbers-they aren't date
+          Zone serial numbers are just numbers &mdash; they aren't date
           related.  A lot of people set them to a number that represents a
-          date, usually of the form YYYYMMDDRR. A number of people have been
-          testing these numbers for Y2K compliance and have set the number
-          to the year 2000 to see if it will work. They then try to restore
-          the old serial number. This will cause problems because serial
+          date, usually of the form YYYYMMDDRR. A number of people
+          tested these numbers for Y2K compliance and set the number
+          to the year 2000 to see if it would work. They then tried to restore
+          the old serial number. This caused problems because serial
           numbers are used to indicate that a zone has been updated. If the
           serial number on the slave server is lower than the serial number
           on the master, the slave server will attempt to update its copy of