From 4ab5256558823856bc7eba0264fc5fbd14a6a020 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Mon, 22 Feb 2010 04:28:04 +0000
Subject: [PATCH] corrected examples

git-svn-id: file:///home/ksmith/gitmigration/svn/xmpp/trunk@3969 4b5297f7-1745-476d-ba37-a9c6900126ab
---
 xep-0115.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xep-0115.xml b/xep-0115.xml
index 396b3e22..9c184782 100644
--- a/xep-0115.xml
+++ b/xep-0115.xml
@@ -495,7 +495,7 @@
   <c xmlns='http://jabber.org/protocol/caps'
      hash='sha-1'
      node='http://jabberd.org'
-     ver='ItBTI0XLDFvVxZ72NQElAzKS9sU='>
+     ver='ItBTI0XLDFvVxZ72NQElAzKS9sU='/>
 </stream:features>
       ]]></example>
       <p>When a connected client or peer server sends a service discovery information request to determine the entity capabilities of a server that advertises capabilities via the stream feature, the requesting entity MUST send the disco#info request to the server's JID as provided in the 'from' attribute of the response stream header (the 'from' attribute was recommended by &rfc3920; and is required by &rfc3920bis;). To enable this functionality, a server that advertises support for entity capabilities MUST provide a 'from' address in its response stream headers, in accordance with <cite>rfc3920bis</cite>.</p>