fix mdashes

note about dashes in readme

reference/en-US/ee.xml

@@ -206,7 +206,7 @@ public void sendMessage(String price) {
       <title>Packaging and deployment</title>
 
       <para>
-         CDI doesn't define any special deployment archive. You can package beans in JARs, EJB-JARs or WARs &#151; any
+         CDI doesn't define any special deployment archive. You can package beans in JARs, EJB-JARs or WARs &#8212; any
          deployment location in the application classpath. However, the archive must be a "bean archive". That means
          each archive that contains beans <emphasis>must</emphasis> include a file named <literal>beans.xml</literal> in
          the <literal>META-INF</literal> directory of the classpath or <literal>WEB-INF</literal> directory of the web

reference/en-US/environments.xml

@@ -79,6 +79,7 @@ $> ant update</programlisting>
          jars: 
       </para>
 
+      <!-- TODO check for accuracy in 1.0 release -->
       <itemizedlist>
          <listitem>
             <para>

reference/en-US/events.xml

@@ -105,7 +105,7 @@ public @interface Updated {}]]></programlisting>
       <programlisting role="JAVA"><![CDATA[public void afterDocumentUpdate(@Observes @Updated Document document) { ... }]]></programlisting>
 
       <para>
-         An observer method need not specify any event qualifiers &#151; in this case it is interested in
+         An observer method need not specify any event qualifiers &#8212; in this case it is interested in
          <emphasis>all</emphasis> events of a particular type. If it does specify event bindings, it's only interested
          in events which also have those qualifiers.
       </para>

reference/en-US/injection.xml

@@ -381,7 +381,7 @@ public class SynchronousReliablePaymentProcessor implements PaymentProcessor {
 
       <para>
          To fix an <literal>UnsatisfiedDependencyException</literal>, simply provide a bean which implements the bean
-         type and has all the qualifier types of the injection point &#151; or explicitly enable an
+         type and has all the qualifier types of the injection point &#8212; or explicitly enable an
          <literal>@Alternative</literal> bean that implements the bean type and has the appropriate qualifier types.
       </para>
 

reference/en-US/interceptors.xml

@@ -278,7 +278,7 @@ public class ShoppingCart {
       <para>
          Well, fortunately, CDI works around this missing feature of Java. We may annotate one interceptor binding type
          with other interceptor binding types (termed a <emphasis>meta-annotation</emphasis>). The interceptor bindings
-         are transitive &#151; any bean with the first interceptor binding inherits the interceptor bindings declared as
+         are transitive &#8212; any bean with the first interceptor binding inherits the interceptor bindings declared as
          meta-annotations.
       </para>
 
@@ -322,7 +322,7 @@ public class ShoppingCart {
          </listitem>
          <listitem>
             <para>
-               the interceptor ordering is non-global &#151; it is determined by the order in which interceptors are
+               the interceptor ordering is non-global &#8212; it is determined by the order in which interceptors are
                listed at the class level.
             </para>
          </listitem>

reference/en-US/part3.xml

@@ -10,7 +10,7 @@
 
    <para>
       You don't see string-based identifiers in CDI code, not because the framework is hiding them from you using clever
-      defaulting rules &#151; so-called "configuration by convention" &#151; but because there are simply no strings
+      defaulting rules &#8212; so-called "configuration by convention" &#8212; but because there are simply no strings
       there to begin with!
    </para>
 

reference/en-US/scopescontexts.xml

@@ -267,7 +267,7 @@ public class OrderBuilder {
          <para>
             The container is permitted to destroy a conversation and all state held in its context at any time in order
             to preserve resources. A CDI implementation will normally do this on the basis of some kind of timeout
-            &#151; though this is not required by the CDI specification. The timeout is the period of inactivity before
+            &#8212; though this is not required by the CDI specification. The timeout is the period of inactivity before
             the conversation is destroyed (as opposed to the amount of time the conversation is active).
          </para>