diff --git a/doc/faq-parse.xml b/doc/faq-parse.xml
index 02dcc0bf0dcb455a9f9e6ee6d100257d222fb138..04c02c0e2fdb2e9642ab10d57b658f4232ff7282 100644
--- a/doc/faq-parse.xml
+++ b/doc/faq-parse.xml
@@ -360,10 +360,18 @@ catch (const XMLException& toCatch) {
     </a>
   </faq>
 
-  <faq title="Why DOMNode::cloneNode() does not clone the pointer assigned to a DOMNode via DOMNode::setUserData()?">
-    <q>Why DOMNode::cloneNode() does not clone the pointer assigned to a DOMNode via DOMNode::setUserData()?</q>
+  <faq title="Why does DOMNode::cloneNode() not clone the pointer assigned to a DOMNode via DOMNode::setUserData()?">
+    <q>Why does DOMNode::cloneNode() not clone the pointer assigned to a DOMNode via DOMNode::setUserData()?</q>
     <a>
-      <p>&XercesCName; supports the DOMNode::userData specified in
+      <p>&XercesCName; supports the DOMNode::userData specified
+      in <jump href="http://www.w3.org/TR/2003/WD-DOM-Level-3-Core-20030226/DOM3-Core.html#core-ID-3A0ED0A4">
+      the DOM level 3 Node interface</jump>.  As
+      is made clear in the description of the behaviour of
+      <code>cloneNode()</code>, userData that has been set on the
+      Node is not cloned.  Thus, if the userData is to be copied
+      to the new Node, this copy must be effected manually.
+      Note further that the operation of <code>importNode()</code>
+      is specified similarly.
       </p>
     </a>
   </faq>