diff --git a/xep-0122.xml b/xep-0122.xml
index be48a6c0..8ad77987 100644
--- a/xep-0122.xml
+++ b/xep-0122.xml
@@ -101,7 +101,7 @@
   </ul>
 </section1>
 <section1 topic='Use Cases' anchor='usecases'>
-  <p>This document defines a new namespace, "http://jabber.org/protocols/xdata-validate". The root element for this namespace is &lt;validate/&gt;, and MUST be contained within a &lt;field/&gt; element (qualified by the 'jabber:x:data' namespace) for each <cite>Data Forms</cite> field that possesses additional validation information.</p>
+  <p>This document defines a new namespace, "http://jabber.org/protocol/xdata-validate". The root element for this namespace is &lt;validate/&gt;, and MUST be contained within a &lt;field/&gt; element (qualified by the 'jabber:x:data' namespace) for each <cite>Data Forms</cite> field that possesses additional validation information.</p>
   <section2 topic='Datatype Validation' anchor='usecases-datatypes'>
     <p>The simplest usage is to provide a more-granular datatype for a &lt;field/&gt; element used in <cite>Data Forms</cite>. To provide this datatype information, a &lt;validate/&gt; element is included whose 'datatype' attribute specifies the data type of any &lt;value/&gt; contained within the &lt;field/&gt; element:</p>
     <example caption='Field with extended datatype'><![CDATA[
@@ -233,7 +233,7 @@
     <p>The use of namespace prefixes is RECOMMENDED for large forms, to reduce the data size. To maintain the highest level of compatibility, implementations sending the form using prefixes SHOULD use the namespace prefix "xdv", and SHOULD declare the namespace prefix mapping in the ancestor &lt;x xmlns='jabber:x:data'/&gt; element:</p>
     <example caption='Example of recommended namespace prefixing'><![CDATA[
 <x xmlns='jabber:x:data'
-   xmlns:xdv='http://jabber.org/protocols/xdata-validate'
+   xmlns:xdv='http://jabber.org/protocol/xdata-validate'
    type='form'>
   <title>Sample Form</title>
   <instructions>