OPENFLOW-1.1+: Fix character encoding issues.

Signed-off-by: Ben Pfaff <blp@nicira.com>

diff --git a/OPENFLOW-1.1+ b/OPENFLOW-1.1+
index ec3924d..b6a4222 100644 (file)
--- a/OPENFLOW-1.1+
+++ b/OPENFLOW-1.1+
@@ -92,7 +92,7 @@ OpenFlow 1.2
 
 OpenFlow 1.2 support requires OpenFlow 1.1 as a prerequisite, plus the
 following additional work.  (This is based on the change log at the
-end of the OF1.2 spec.  I didn’t compare the specs carefully yet.)
+end of the OF1.2 spec.  I didn't compare the specs carefully yet.)
 
     * Use new OpenFlow extensible error infrastructure, on OF1.2+
       only, instead of the OVS-specific extension used until now.
@@ -121,7 +121,7 @@ OpenFlow 1.3
 OpenFlow 1.3 support requires OpenFlow 1.2 as a prerequisite, plus the
 following additional work.  (This is based on the change log at the
 end of the OF1.3 spec, reusing most of the section titles directly.  I
-didn’t compare the specs carefully yet.)
+didn't compare the specs carefully yet.)
 
     * Add support for multipart requests.
 
@@ -138,7 +138,7 @@ didn’t compare the specs carefully yet.)
       and design requirements.  Might be politically difficult to add
       directly to the kernel module, since its functionality overlaps
       with tc.  Ideally, therefore, we could implement these somehow
-      with tc, but I haven’t investigated whether that makes sense.
+      with tc, but I haven't investigated whether that makes sense.
 
     * Per-connection event filtering.  OF1.3 adopted Open vSwitch's
       existing design for this feature so implementation should be
@@ -146,20 +146,20 @@ didn’t compare the specs carefully yet.)
 
     * Auxiliary connections.  These are optional, so a minimal
       implementation would not need them.  An implementation in
-      generic code might be a week’s worth of work.  The value of an
+      generic code might be a week's worth of work.  The value of an
       implementation in generic code is questionable, though, since
       much of the benefit of axuiliary connections is supposed to be
       to take advantage of hardware support.  (We could make the
       kernel module somehow send packets across the auxiliary
-      connections directly, for some kind of “hardware” support, if we
+      connections directly, for some kind of "hardware" support, if we
       judged it useful enough.)
 
     * MPLS BoS matching.  (Included in Simon's MPLS series?)
 
-    * Provider Backbone Bridge tagging.  I don’t plan to implement
-      this (but we’d accept an implementation).
+    * Provider Backbone Bridge tagging.  I don't plan to implement
+      this (but we'd accept an implementation).
 
-    * Rework tag order.  I’m not sure whether we need to do anything
+    * Rework tag order.  I'm not sure whether we need to do anything
       for this.
 
     * Duration for stats.
@@ -192,7 +192,7 @@ Please consider the following:
       tree).
 
     * The patch submission guidelines (see SubmittingPatches).  I
-      recommend using “git send-email”, which automatically follows a
+      recommend using "git send-email", which automatically follows a
       lot of those guidelines.
 
 Bug Reporting