[EME] Minor corrections.
--- a/encrypted-media/encrypted-media.html Tue May 07 12:22:17 2013 -0700
+++ b/encrypted-media/encrypted-media.html Wed May 08 14:20:06 2013 -0700
@@ -901,7 +901,7 @@
<p><i>This section is non-normative.</i></p>
<p>The above sections provide for delivery of key/license information to a <a href="#cdm">Content Decryption Module</a>.
This section provides for management of the entire key/license lifecycle, that is, secure proof of key release.
- Use cases for such proof include any service where is it necessary for the service to know, reliably, which granted keys/licences are still available for use by the user and which have been deleted.
+ Use cases for such proof include any service where is it necessary for the service to know, reliably, which granted keys/licenses are still available for use by the user and which have been deleted.
Examples include a service with restrictions on the number of concurrent streams available to a user or a service where content is available on a rental basis, for use offline.
</p>
@@ -1218,7 +1218,7 @@
</div>
<h3 id="example-using-all-events" class="exampleheader">8.4. Using All Events</h3>
- <p class="exampledescription">This is a more complete example showing all events being used along with asynchronous XHR.</p>
+ <p class="exampledescription">This is a more complete example showing all events being used.</p>
<p class="exampledescription">Note that <code>handleKeyMessage</code> could be called multiple times, including in response to the <code><a href="#dom-update">update()</a></code> call if multiple round trips are required and for any other reason the Key System might need to send a message.</p>
<div class="example">
--- a/encrypted-media/encrypted-media.xml Tue May 07 12:22:17 2013 -0700
+++ b/encrypted-media/encrypted-media.xml Wed May 08 14:20:06 2013 -0700
@@ -845,7 +845,7 @@
<non-normative-section/>
<p>The above sections provide for delivery of key/license information to a <a href="#cdm">Content Decryption Module</a>.
This section provides for management of the entire key/license lifecycle, that is, secure proof of key release.
- Use cases for such proof include any service where is it necessary for the service to know, reliably, which granted keys/licences are still available for use by the user and which have been deleted.
+ Use cases for such proof include any service where is it necessary for the service to know, reliably, which granted keys/licenses are still available for use by the user and which have been deleted.
Examples include a service with restrictions on the number of concurrent streams available to a user or a service where content is available on a rental basis, for use offline.
</p>
@@ -1162,7 +1162,7 @@
</div>
<h3 id="example-using-all-events" class="exampleheader">8.4. Using All Events</h3>
- <p class="exampledescription">This is a more complete example showing all events being used along with asynchronous XHR.</p>
+ <p class="exampledescription">This is a more complete example showing all events being used.</p>
<p class="exampledescription">Note that <code>handleKeyMessage</code> could be called multiple times, including in response to the <methodref>update</methodref> call if multiple round trips are required and for any other reason the Key System might need to send a message.</p>
<div class="example">