From 2ad7289de50f0aa56e063856ff0712cd18e9433c Mon Sep 17 00:00:00 2001
From: Peter Saint-Andre <stpeter@jabber.org>
Date: Tue, 13 Apr 2010 21:23:08 +0000
Subject: [PATCH] text tweaks

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

diff --git a/xep-0234.xml b/xep-0234.xml
index c271844e..0a9f884d 100644
--- a/xep-0234.xml
+++ b/xep-0234.xml
@@ -325,15 +325,15 @@ Initiator                    Responder
 </iq>
   ]]></example>
   <p>The parties would then complete a session negotiation flow similar to that outlined above for offering a file.</p>
-  <p>Note: If the requesting entity knows the hash of the file, then it can include only that metadata in its request. If not, the requesting entity needs include enough metadata to uniquely identify the file, such as the date, name, and size. For similar considerations, see &rfc5547;.</p>
+  <p>Note: If the requesting entity knows the hash of the file, then it can include only that metadata in its request. If not, the requesting entity needs to include enough metadata to uniquely identify the file, such as the date, name, and size. For similar considerations, see &rfc5547;.</p>
 </section1>
 
 <section1 topic='Implementation Notes' anchor='impl'>
   <section2 topic='Mandatory to Implement Technologies' anchor='impl-mti'>
-    <p>All implementations MUST support the In-Band Bytestreams transport method as a reliable method of last resort. An implementation SHOULD support other transport methods as well, especially SOCKS5 Bytestreams.</p>
+    <p>All implementations MUST support the Jingle In-Band Bytestreams Transport Method (<cite>XEP-0261</cite>) as a reliable method of last resort. An implementation SHOULD support other transport methods as well, especially the Jingle SOCKS5 Bytestreams Transport Method (<cite>XEP-0260</cite>).</p>
   </section2>
   <section2 topic='Preference Order of Transport Methods' anchor='impl-pref'>
-    <p>An application MAY present transport methods in any order, except that the In-Band Bytestreams method MUST be the lowest preference.</p>
+    <p>An application MAY present transport methods in any order, except that the Jingle In-Band Bytestreams Transport Method MUST be the lowest preference.</p>
   </section2>
   <section2 topic='Migration from XEP-0096' anchor='impl-migration'>
     <p>Support for Jingle file transfer can be determined through discovery of the 'urn:xmpp:jingle:apps:file-transfer:1' namespace &VNOTE;, via either service discovery (<cite>XEP-0030</cite>) or entity capabilities (<cite>XEP-0115</cite>). If the initiator knows that the responder supports Jingle file transfer, it SHOULD first attempt negotiation using Jingle rather than SI.</p>
@@ -342,6 +342,7 @@ Initiator                    Responder
 
 <section1 topic='Security Considerations' anchor='security'>
   <p>In order to secure the data stream, implementations SHOULD use encryption methods appropriate to the transport method being used. For example, end-to-end encryption can be negotiated over either SOCKS5 Bytestreams or In-Band Bytestreams as described in <cite>XEP-0260</cite> and <cite>XEP-0261</cite>.</p>
+  <p>Refer to <cite>XEP-0047</cite>, <cite>XEP-0065</cite>, <cite>XEP-0096</cite>, <cite>XEP-0260</cite>, and <cite>XEP-0261</cite> for related security considerations.</p>
 </section1>
 
 <section1 topic='IANA Considerations' anchor='iana'>