diff --git a/xep-0221.xml b/xep-0221.xml
index 86ab1a21..e1ca737a 100644
--- a/xep-0221.xml
+++ b/xep-0221.xml
@@ -43,13 +43,19 @@
 <section1 topic='Media Element' anchor='media'>
   <p>The root element for media data is &lt;media/&gt;. This element MUST be qualified by the "urn:xmpp:tmp:media-element' namespace &NSNOTE;. The &lt;media/&gt; element MUST be contained within a &lt;field/&gt; element qualified by the 'jabber:x:data' namespace.</p>
   <p>If the media is an image or video then the &lt;media/&gt; element SHOULD include 'height' and 'width' attributes specifying the recommended display size of the media in pixels.</p>
-  <p>The &lt;media/&gt; element SHOULD contain at least one &lt;uri/&gt; element to specify the out-of-band location of the media data. <note>Constrained execution environments prevent some clients (e.g., Web clients) from rendering media unless it has been received out-of-band.</note> The &lt;uri/&gt; element MUST contain a URI that indicates the location and MUST include a 'type' atribute that specifies the MIME type (see &rfc2045;) of the media.</p>
+  <p>The &lt;media/&gt; element MUST contain at least one &lt;uri/&gt; element to specify the out-of-band location of the media data. <note>Constrained execution environments prevent some clients (e.g., Web clients) from rendering media unless it has been received out-of-band.</note> The &lt;uri/&gt; element MUST contain a URI that indicates the location and MUST include a 'type' atribute that specifies the MIME type (see &rfc2045;) of the media.</p>
   <p>The &lt;media/&gt; element MAY also contain one or more &lt;data/&gt; elements for distributing the media in-band. The &lt;data/&gt; element MUST be qualified by the 'urn:xmpp:tmp:data-element' as defined in &xep0231;. The <em>encoded</em> data SHOULD NOT be larger than 8 kilobytes. <note>If a stanza contains more than one &lt;data/&gt; element, the sending entity MUST take care not to trigger server-defined bandwidth limits.</note></p>
   <example caption='Audio Media Element'><![CDATA[
 <media xmlns='urn:xmpp:tmp:media-element'>
-  <uri type='audio/x-wav'>http://victim.example.com/challenges/speech.wav?F3A6292C</uri>
-  <uri type='audio/ogg-speex'>http://victim.example.com/challenges/speech.ogg?F3A6292C</uri>
-  <uri type='audio/mpeg'>http://victim.example.com/challenges/speech.mp3?F3A6292C</uri>
+  <uri type='audio/x-wav'>
+    http://victim.example.com/challenges/speech.wav?F3A6292C
+  </uri>
+  <uri type='audio/ogg-speex'>
+    http://victim.example.com/challenges/speech.ogg?F3A6292C
+  </uri>
+  <uri type='audio/mpeg'>
+    http://victim.example.com/challenges/speech.mp3?F3A6292C
+  </uri>
   <data xmlns='urn:xmpp:tmp:data-element' 
         alt='An audio file'
         type='audio/x-wav'>
@@ -57,6 +63,24 @@
   </data>
 </media>
   ]]></example>
+  <p>The following example is provided only for the purpose of illustration; consult the specifications for using protocols to see canonical examples.</p>
+  <example caption='Inclusion in Data Form'><![CDATA[
+<x xmlns='jabber:x:data' type='form'>
+  [ ... ]
+  <field var='ocr'>
+    <media xmlns='xmlns='urn:xmpp:tmp:media-element'
+           height='80'
+           width='290'>
+      <uri type='image/jpeg'>
+        http://www.victim.com/challenges/ocr.jpeg?F3A6292C
+      </uri>
+      <data xmlns='urn:xmpp:tmp:data-element'
+            type='image/jpeg'> ** Base64 encoded image ** </data>
+    </media>
+  </field>
+  [ ... ]
+</x>
+  ]]></example>
 </section1>
 
 <section1 topic='XMPP Registrar Considerations' anchor='registrar'>