--- a/encrypted-media/encrypted-media.html	Sat Sep 01 15:38:11 2012 -0700
+++ b/encrypted-media/encrypted-media.html	Sat Sep 01 15:48:15 2012 -0700
@@ -1106,18 +1106,18 @@
   var licenseUrl;
 
   function selectKeySystem(video) {
-    if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem") != “”) {
-      licenseUrl = “https://license.example.com/getkey”; // OR “https://example.&lt;My Video Site domain&gt;”
-      if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.2_0") != “”) {
-        keySystem = “com.example.somesystem.2_0”;
-      } else if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.1_5") != “”) {
-        keySystem = “com.example.somesystem.1_5”;
+    if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem") != "") {
+      licenseUrl = "https://license.example.com/getkey"; // OR "https://example.&lt;My Video Site domain&gt;"
+      if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.2_0") != "") {
+        keySystem = "com.example.somesystem.2_0";
+      } else if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.1_5") != "") {
+        keySystem = "com.example.somesystem.1_5";
       }
-    } else if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "foobar") != “” {
-      licenseUrl = “https://license.foobar.com/request”;
-      keySystem = “foobar”;
+    } else if (video.<a href="#dom-canplaytype">canPlayType</a>("video/webm; codecs='vp8, vorbis'", "foobar") != "" {
+      licenseUrl = "https://license.foobar.com/request";
+      keySystem = "foobar";
     } else {
-      throw “Key System not supported”;
+      throw "Key System not supported";
     }
   }
 
@@ -1292,7 +1292,7 @@
     As shown in the <a href="#examples">examples</a>, the basic use cases are reasonably simple and only require a little setup to get the key and provide it to the user agent.
     We believe most small content sites can add basic protection to their applications with minimal efforts.</p>
     <p class="faqanswer">The more complex cases, such as fast time to first frame and various license management algorithms, require more complex code, but professional-strength content protection is complex and that is to be expected.
-    Professional-strength content protection requires server components and working with one or more content protection vendors, so this isn’t really any more complex.
+    Professional-strength content protection requires server components and working with one or more content protection vendors, so this isn't really any more complex.
     In fact, if you implement a few solutions, it will work on any browser-based platform, avoiding the need for per-platform solutions on both the server and client.
     The fixed set of interfaces may even lead to more consistent patterns and behavior across various solutions.
     It is generally the large content providers that have more complex requirements, and we believe they will have the appropriate resources to implement applications that meet their requirements.

--- a/encrypted-media/encrypted-media.xml	Sat Sep 01 15:38:11 2012 -0700
+++ b/encrypted-media/encrypted-media.xml	Sat Sep 01 15:48:15 2012 -0700
@@ -1050,18 +1050,18 @@
   var licenseUrl;
 
   function selectKeySystem(video) {
-    if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem") != “”) {
-      licenseUrl = “https://license.example.com/getkey”; // OR “https://example.&lt;My Video Site domain&gt;”
-      if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.2_0") != “”) {
-        keySystem = “com.example.somesystem.2_0”;
-      } else if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.1_5") != “”) {
-        keySystem = “com.example.somesystem.1_5”;
+    if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem") != "") {
+      licenseUrl = "https://license.example.com/getkey"; // OR "https://example.&lt;My Video Site domain&gt;"
+      if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.2_0") != "") {
+        keySystem = "com.example.somesystem.2_0";
+      } else if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "com.example.somesystem.1_5") != "") {
+        keySystem = "com.example.somesystem.1_5";
       }
-    } else if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "foobar") != “” {
-      licenseUrl = “https://license.foobar.com/request”;
-      keySystem = “foobar”;
+    } else if (video.<premethodref>canPlayType</premethodref>("video/webm; codecs='vp8, vorbis'", "foobar") != "" {
+      licenseUrl = "https://license.foobar.com/request";
+      keySystem = "foobar";
     } else {
-      throw “Key System not supported”;
+      throw "Key System not supported";
     }
   }
 
@@ -1236,7 +1236,7 @@
     As shown in the <a href="#examples">examples</a>, the basic use cases are reasonably simple and only require a little setup to get the key and provide it to the user agent.
     We believe most small content sites can add basic protection to their applications with minimal efforts.</p>
     <p class="faqanswer">The more complex cases, such as fast time to first frame and various license management algorithms, require more complex code, but professional-strength content protection is complex and that is to be expected.
-    Professional-strength content protection requires server components and working with one or more content protection vendors, so this isn’t really any more complex.
+    Professional-strength content protection requires server components and working with one or more content protection vendors, so this isn't really any more complex.
     In fact, if you implement a few solutions, it will work on any browser-based platform, avoiding the need for per-platform solutions on both the server and client.
     The fixed set of interfaces may even lead to more consistent patterns and behavior across various solutions.
     It is generally the large content providers that have more complex requirements, and we believe they will have the appropriate resources to implement applications that meet their requirements.