--- a/encrypted-media/encrypted-media.html	Mon Nov 11 17:39:27 2013 +0800
+++ b/encrypted-media/encrypted-media.html	Mon Nov 11 17:40:41 2013 +0800
@@ -450,7 +450,7 @@
       </li>
       <li>Return the new object to the caller.</li>
       <p class="non-normative">Note: User agents should always fire an event at the returned object in response to this call.
-      For some implementations, it is possible - especially the first time a <a href="#key-system">Key System</a> is used - that the first event will be delayed significantly while the client is initialized, the user responsds to permission requests, etc.
+      For some implementations, it is possible - especially the first time a <a href="#key-system">Key System</a> is used - that the first event will be delayed significantly while the client is initialized, the user responds to permission requests, etc.
       Applications should expect and handle such delays.</p> 
     </ol>
 

--- a/encrypted-media/encrypted-media.xml	Mon Nov 11 17:39:27 2013 +0800
+++ b/encrypted-media/encrypted-media.xml	Mon Nov 11 17:40:41 2013 +0800
@@ -437,7 +437,7 @@
       </li>
       <li>Return the new object to the caller.</li>
       <p class="non-normative">Note: User agents should always fire an event at the returned object in response to this call.
-      For some implementations, it is possible - especially the first time a <a href="#key-system">Key System</a> is used - that the first event will be delayed significantly while the client is initialized, the user responsds to permission requests, etc.
+      For some implementations, it is possible - especially the first time a <a href="#key-system">Key System</a> is used - that the first event will be delayed significantly while the client is initialized, the user responds to permission requests, etc.
       Applications should expect and handle such delays.</p> 
     </ol>