Convert a number of hyphens in to m-dashes.

doc/arm/1intro.xml

@@ -203,7 +203,7 @@ There there will be some number of <emphasis>slave</emphasis> (also
 called <emphasis>secondary) </emphasis>servers, which load the zone
 contents using the <acronym>DNS</acronym> protocol (that is, the secondary servers
 will contact the primary and fetch the zone data using TCP). This
-set of servers-the primary and all of its secondaries-should be
+set of servers &mdash; the primary and all of its secondaries &mdash; should be
 listed in the NS records in the parent zone and will constitute a <emphasis>delegation</emphasis>.
 This set of servers must also be listed in the zone file itself,
 usually under the <command>@</command> name which indicates the <emphasis>top
@@ -218,8 +218,8 @@ configured to answer questions for that zone with authority, which
 it does by setting the "authoritative answer" (AA) bit in reply
 packets. A server may be authoritative for more than one zone. The
 authoritative data for a zone is composed of all of the Resource
-Records (RRs)-the data associated with names in a tree-structured
-name space-attached to all of the nodes from the top node of the
+Records (RRs) &mdash; the data associated with names in a tree-structured
+name space &mdash; attached to all of the nodes from the top node of the
 zone down to leaf nodes or nodes above cuts around the bottom edge
 of the zone.</para>
 <para>Adding a zone as a type master or type slave will tell the

doc/arm/2res-req.xml

@@ -19,7 +19,7 @@ cache and zones loaded off disk. Future releases of <acronym>BIND</acronym> 9 wi
 provide methods to limit the amount of memory used by the cache,
 at the expense of reducing cache hit rates and causing more <acronym>DNS</acronym>
 traffic. It is still good practice to have enough memory to load
-all zone and cache data into memory-unfortunately, the best way
+all zone and cache data into memory &mdash; unfortunately, the best way
 to determine this for a given installation is to watch the nameserver
 in operation. After a few weeks the server process should reach
 a relatively stable size where entries are expiring from the cache as

doc/arm/6configref.xml

@@ -2540,10 +2540,10 @@ controls the order in which email delivery is attempted, with the
 lowest number first. If two priorities are the same, a server is
 chosen randomly. If no servers at a given priority are responding,
 the mail transport agent will fall back to the next largest priority.
-Priority numbers do not have any absolute meaning - they are relevant
+Priority numbers do not have any absolute meaning — they are relevant
 only respective to other MX records for that domain name. The domain
 name given is the machine to which the mail will be delivered. It <emphasis>must</emphasis> have
-an associated A record-a CNAME is not sufficient.</para>
+an associated A record &mdash; CNAME is not sufficient.</para>
 <para>For a given domain, if there is both a CNAME record and an
 MX record, the MX record is in error, and will be ignored. Instead,
 the mail will be delivered to the server specified in the MX record

doc/arm/9appendices.xml

@@ -267,7 +267,7 @@ the number of the RFC). RFCs are also available via the Web at <ulink
               <surname>Mockapetris</surname>
               <firstname>P.V.</firstname>
             </author> 
-            <title>Domain Names - Concepts and Facilities</title>
+            <title>Domain Names &mdash; Concepts and Facilities</title>
             <pubdate>November 1987</pubdate>
           </biblioentry>
           <biblioentry>
@@ -275,7 +275,7 @@ the number of the RFC). RFCs are also available via the Web at <ulink
             <author>
               <surname>Mockapetris</surname>
               <firstname>P. V.</firstname>
-            </author> <title>Domain Names - Implementation and
+            </author> <title>Domain Names &mdash; Implementation and
 Specification</title>
             <pubdate>November 1987</pubdate>
           </biblioentry>