From da18fd4ccdd0d72cf56d5bf03def64d9550f406b Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Wed, 10 Mar 2010 04:31:59 +0000
Subject: [PATCH] corrected a reference

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

diff --git a/xep-0136.xml b/xep-0136.xml
index f04ad1e5..976b13d7 100644
--- a/xep-0136.xml
+++ b/xep-0136.xml
@@ -301,7 +301,7 @@
 	<p>If the client wants to keep this rule longer, it must send a new &lt;session/&gt; element to the server before this timeout expires.</p>
       </section4>
       <section4 topic='thread Attribute' anchor='pref-syntax-thread'>
-        <p>The 'thread' attribute specifies the ThreadID of the chat session (in the sense of &xep-0155;) to which the preferences specified in this &lt;session/&gt; element apply.</p>
+        <p>The 'thread' attribute specifies the ThreadID of the chat session (in the sense of &xep0155;) to which the preferences specified in this &lt;session/&gt; element apply.</p>
       </section4>
       <section4 topic='save Attribute' anchor='pref-syntax-session-save'>
         <p>The 'save' attribute specifies the user's setting for Save Mode with regard to the specified chat session. The allowable values are:</p>
@@ -449,7 +449,7 @@
     ]]></example>
   </section2>
   <section2 topic='Setting Modes for a Chat Session' anchor='pref-session'>
-	  <p>A client may use a similar protocol to set the Modes for a particular chat session. A chat session is identified by its unique 'thread' attributes in &lt;message&gt; stanza (see &xep0155;)</p>
+	  <p>A client may use a similar protocol to set the Modes for a particular chat session. A chat session is identified by its unique 'thread' attributes in &lt;message&gt; stanza (see <cite>XEP-0155</cite>).</p>
     <example caption='Client Sets Modes for a Chat Session'><![CDATA[
 <iq type='set' id='pref4'>
   <pref xmlns='urn:xmpp:archive'>
@@ -1243,7 +1243,7 @@
 
 <section1 topic='Security Considerations' anchor='security'>
   <section2 topic='Automatic Archiving Defaulting to On' anchor='security-autoon'>
-    <p>If automatic archiving defaults to enabled then that creates serious privacy issues for users of legacy clients that do not support this protocol, and (more seriously) for those contacts who they unwittingly mislead by agreeing to disable logging (via the 'logging' field defined in &xep0155;).</p>
+    <p>If automatic archiving defaults to enabled then that creates serious privacy issues for users of legacy clients that do not support this protocol, and (more seriously) for those contacts who they unwittingly mislead by agreeing to disable logging (via the 'logging' field defined in <cite>XEP-0155</cite>).</p>
     <p>If a server deployment enables automatic archiving by default, then it MUST return a stream feature containing an empty &lt;default/&gt; element (see the <link url='#streamfeature'>Stream Feature</link> section of this document).</p>
   </section2>
   <section2 topic='Store Headers' anchor='security-store'>