From e256a4d339383f3bd8445f580a6a7fce9033bf18 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Wed, 13 Jan 2010 22:56:14 +0000
Subject: [PATCH] a clarification to reduce confusion

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3826 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0106.xml | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/xep-0106.xml b/xep-0106.xml
index 4895a857..3528d6b1 100644
--- a/xep-0106.xml
+++ b/xep-0106.xml
@@ -120,7 +120,7 @@
     <p>Note: All transformations are exactly as specified below. CASE IS SIGNIFICANT. Lowercase was selected since Nodeprep will case fold to lowercase for US-ASCII characters such as A, C, E, and F.</p>
   </section2>
   <section2 topic='Escaping Transformations' anchor='escaping'>
-    <p>The escaping transformations are defined in the following table. Typically, escaping is performed only by a client that is processing information provided by a human user in unescaped form, or by a gateway to some external system (e.g., email or LDAP) that needs to generate a JID.</p>
+    <p>The escaping transformations are defined in the following table, whereas the rules that define when to apply these transformations are specified in the <link url='#bizrules'>Business Rules</link> section of this specification. Typically, escaping is performed only by a client that is processing information provided by a human user in unescaped form, or by a gateway to some external system (e.g., email or LDAP) that needs to generate a JID.</p>
     <table caption='Mapping from Unescaped to Escaped Characters'>
       <tr><th>Unescaped Character</th><th>Escaped Character</th></tr>
       <tr><td>&lt;space&gt;</td><td>\20 *</td></tr>
@@ -146,7 +146,7 @@
     ]]></example>
   </section2>
   <section2 topic='Unescaping Transformations' anchor='unescaping'>
-    <p>The unescaping transformations are defined in the following table. Typically, unescaping is performed only by a client that wants to display JIDs containing escaped characters to a human user, or by a gateway to some external system (e.g., email or LDAP) that needs to generate identifiers for foreign systems.</p>
+    <p>The unescaping transformations are defined in the following table, whereas the rules that define when to apply these transformations are specified in the <link url='#bizrules'>Business Rules</link> section of this specification. Typically, unescaping is performed only by a client that wants to display JIDs containing escaped characters to a human user, or by a gateway to some external system (e.g., email or LDAP) that needs to generate identifiers for foreign systems.</p>
     <table caption='Mapping from Escaped to Unescaped Characters'>
       <tr><th>Escaped Character</th><th>Unescaped Character</th></tr>
       <tr><td>\20</td><td>&lt;space&gt;</td></tr>