--- a/encrypted-media/encrypted-media.html	Tue Oct 15 08:17:22 2013 -0700
+++ b/encrypted-media/encrypted-media.html	Tue Oct 15 08:23:32 2013 -0700
@@ -169,11 +169,13 @@
 
     <h2 id="introduction">1. Introduction</h2>
     <p><i>This section is non-normative.</i></p>
-    <p>This proposal allows JavaScript to select content protection mechanisms, control license/key exchange, and implement custom license management algorithms.
-    It supports a wide range of use cases without requiring client-side modifications in each user agent for each use case.
-    This also enables content providers to develop a single application solution for all devices.
-    A generic stack implemented using the proposed APIs is shown below.
-    This is just an example flow and is not intended to show all possible communication or uses.</p>
+    <p>
+      This proposal allows JavaScript to select content protection mechanisms, control license/key exchange, and implement custom license management algorithms.
+      It supports a wide range of use cases without requiring client-side modifications in each user agent for each use case.
+      This also enables content providers to develop a single application solution for all devices.
+      A generic stack implemented using the proposed APIs is shown below.
+      This diagram shows an example flow: other combinations of API calls and events are possible.
+    </p>
     <img src="stack_overview.png" alt="A generic stack implemented using the proposed APIs" height="700">
 
     <h3 id="definitions">1.1. Definitions</h3>

--- a/encrypted-media/encrypted-media.xml	Tue Oct 15 08:17:22 2013 -0700
+++ b/encrypted-media/encrypted-media.xml	Tue Oct 15 08:23:32 2013 -0700
@@ -166,11 +166,13 @@
 
     <h2 id="introduction">1. Introduction</h2>
     <non-normative-section/>
-    <p>This proposal allows JavaScript to select content protection mechanisms, control license/key exchange, and implement custom license management algorithms.
-    It supports a wide range of use cases without requiring client-side modifications in each user agent for each use case.
-    This also enables content providers to develop a single application solution for all devices.
-    A generic stack implemented using the proposed APIs is shown below.
-    This is just an example flow and is not intended to show all possible communication or uses.</p>
+    <p>
+      This proposal allows JavaScript to select content protection mechanisms, control license/key exchange, and implement custom license management algorithms.
+      It supports a wide range of use cases without requiring client-side modifications in each user agent for each use case.
+      This also enables content providers to develop a single application solution for all devices.
+      A generic stack implemented using the proposed APIs is shown below.
+      This diagram shows an example flow: other combinations of API calls and events are possible.
+    </p>
     <img src="stack_overview.png" alt="A generic stack implemented using the proposed APIs" height="700"></img>
 
     <h3 id="definitions">1.1. Definitions</h3>