From ae459a0f7cfa9119edc23ee15fbd30c2b53e67a5 Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@stpeter.im>
Date: Thu, 13 Dec 2012 06:42:45 -0800
Subject: [PATCH] another small text correction

---
 xep-0262.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/xep-0262.xml b/xep-0262.xml
index ca28c477..6f4dceab 100755
--- a/xep-0262.xml
+++ b/xep-0262.xml
@@ -208,7 +208,7 @@ a=zrtp-hash:1.10 fe30efd02423cb054e50efd0248742ac7a52c8f91bc2df881ae642c371ba46d
 
 <section1 topic='Security Considerations' anchor='security'>
   <p>Security considerations for ZRTP itself are provided in <cite>RFC 6189</cite>.</p>
-  <p>XMPP stanzas such as Jingle session-info messages and service discovery exchanges are not encrypted or signed. As a result, it is possible for an attacker to intercept these stanzas and modify them, thus convincing one party that the other party does not support ZRTP and therefore denying the parties an opportunity to use ZRTP. However, because the zrtp-hash is mostly advisory, the parties could still use ZRTP even if the signalling channel is compromised.</p>
+  <p>XMPP stanzas such as Jingle invite messages and service discovery exchanges are not encrypted or signed. As a result, it is possible for an attacker to intercept these stanzas and modify them, thus convincing one party that the other party does not support ZRTP and therefore denying the parties an opportunity to use ZRTP. However, because the zrtp-hash is mostly advisory, the parties could still use ZRTP even if the signalling channel is compromised.</p>
 </section1>
 
 <section1 topic='IANA Considerations' anchor='iana'>