[asterisk-commits] file: branch file/chan_jingle2 r365686 - /team/file/chan_jingle2/configs/

[SVN commits to the Asterisk project]

Author: file
Date: Tue May  8 14:10:15 2012
New Revision: 365686

URL: http://svnview.digium.com/svn/asterisk?view=rev&rev=365686
Log:
Tweak file based on feedback from that Leif Madsen guy.

Modified:
    team/file/chan_jingle2/configs/jingle2.conf.sample

Modified: team/file/chan_jingle2/configs/jingle2.conf.sample
URL: http://svnview.digium.com/svn/asterisk/team/file/chan_jingle2/configs/jingle2.conf.sample?view=diff&rev=365686&r1=365685&r2=365686
==============================================================================
--- team/file/chan_jingle2/configs/jingle2.conf.sample (original)
+++ team/file/chan_jingle2/configs/jingle2.conf.sample Tue May  8 14:10:15 2012
@@ -2,17 +2,17 @@
 
 ; Transports
 ;
-; There are three different transports and protocol derivatives supported by chan_jingle2. They are (in preference)
+; There are three different transports and protocol derivatives supported by chan_jingle2. They are in order of preference:
 ; Jingle using ICE-UDP, Google Jingle, and Google-V1.
 ;
 ; Jingle as defined in XEP-0166 supports the widest range of features. It is referred to as "ice-udp" in this file. This is
 ; the specification that Jingle clients implement.
 ;
-; Google Jingle follows the Jingle specification for signaling but uses a custom transport for media. It is suppored
+; Google Jingle follows the Jingle specification for signaling but uses a custom transport for media. It is supported
 ; by the Google Talk Plug-in in gmail and by some other Jingle clients. It is referred to as "google" in this file.
 ;
 ; Google-V1 is the original Google Talk signaling protocol which used an initial very preliminary version of Jingle.
-; It also uses the same custom transport as Google Jingle for media. It is suppored by Google Voice, some other Jingle
+; It also uses the same custom transport as Google Jingle for media. It is supported by Google Voice, some other Jingle
 ; clients, and the Windows Google Talk client. It is referred to as "google-v1" in this file.
 ;
 ; Incoming sessions will automatically switch to the correct transport once it has been determined.