summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorJonny Lamb <jonny.lamb@collabora.co.uk>2010-12-07 14:58:41 +0000
committerJonny Lamb <jonny.lamb@collabora.co.uk>2010-12-07 14:58:59 +0000
commite8bb9ed7bbf418f1cdcbb19f44fb3a007915cea2 (patch)
tree4f6ca6f2a3e5b1f9a308bfea501f93d2500062ec
parent6338f2c91dcdde87dd6a4d08de3d37e0aed3ba89 (diff)
protocol: wording updates
Courtesy of Mr. McVittie. Signed-off-by: Jonny Lamb <jonny.lamb@collabora.co.uk>
-rw-r--r--spec/Protocol.xml8
1 files changed, 4 insertions, 4 deletions
diff --git a/spec/Protocol.xml b/spec/Protocol.xml
index 652322b4..4eba0cc7 100644
--- a/spec/Protocol.xml
+++ b/spec/Protocol.xml
@@ -438,9 +438,9 @@ allowed=org.freedesktop.Telepathy.Channel.TargetHandle;org.freedesktop.Telepathy
what kind of authentication channels can possibly appear
before the connection reaches the CONNECTED state.</p>
- <p>The channel type of the authentication channel should be
- the interface added to this list, but if it doesn't make sense
- to do so, a specific interface can be used instead. For example,
+ <p>These can either be channel types, or where the channel
+ type isn't enough information to be useful, interfaces
+ indicating a specific use of a channel type. For example,
<tp:dbus-ref namespace="ofdT.Channel.Type">ServerTLSConnection</tp:dbus-ref>
channels are obviously about TLS certificates so the channel
type would appear in this list. However, a
@@ -451,7 +451,7 @@ allowed=org.freedesktop.Telepathy.Channel.TargetHandle;org.freedesktop.Telepathy
<tp:dbus-ref namespace="ofdT.Channel.Type">ServerAuthentication.AuthenticationMethod</tp:dbus-ref>
property in this list.</p>
- <p>For example, a protocol's
+ <p>For example, if a protocol's
<tp:member-ref>AuthenticationTypes</tp:member-ref> contains
two values:</p>