[Telepathy-commits] [telepathy-spec/master] ConnectionManager: rewrap well-known parameter list

[Will Thompson]

---
 spec/Connection_Manager.xml |   54 +++++++++++++++++++++++++-----------------
 1 files changed, 32 insertions(+), 22 deletions(-)

diff --git a/spec/Connection_Manager.xml b/spec/Connection_Manager.xml
index 7aaba29..a1b18d8 100644
--- a/spec/Connection_Manager.xml
+++ b/spec/Connection_Manager.xml
@@ -249,35 +249,45 @@ Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301, USA.</
           <dt>account (s)</dt>
           <dd>The identifier for the user's account on the server</dd>
 
-          <dt>server (s)</dt><dd>A fully qualified domain name or numeric IPv4 or IPv6
-        address. Using the fully-qualified domain name form is recommended
-        whenever possible. If this parameter is specified and the account
-        for that protocol also specifies a server, this parameter should
-        override that in the user id.</dd>
-
-      <dt>port (q)</dt><dd>A TCP or UDP port number. If this parameter is specified
-        and the account for that protocol also specifies a port, this
-        parameter should override that in the account.</dd>
-
-      <dt>password (s)</dt><dd>A password associated with the account.</dd>
-
-      <dt>require-encryption (b)</dt><dd>Require encryption for this connection. A
-        connection should fail to connect if require-encryption is set
-        and an encrypted connection is not possible.</dd>
-
-      <dt>register (b)</dt><dd>This account should be created on the server if it
-        does not already exist.</dd>
-
-      <dt>ident (s)</dt><dd>The local username to report to the server if
-        necessary, such as in IRC.</dd>
-
-      <dt>fullname (s)</dt><dd>The user's full name if the service requires this
-        when authenticating or registering.</dd>
-
-      <dt>stun-server (s)</dt><dd>The IP address or FQDN of a STUN server to use
-        for NAT traversal, without any ":port" suffix.</dd>
-      <dt>stun-port (q)</dt><dd>The UDP port number on the stun-server to use for
-        STUN. Only significant if the stun-server is also supplied.</dd>
+          <dt>server (s)</dt>
+          <dd>A fully qualified domain name or numeric IPv4 or IPv6 address.
+            Using the fully-qualified domain name form is recommended whenever
+            possible. If this parameter is specified and the account for that
+            protocol also specifies a server, this parameter should override
+            that in the user id.</dd>
+
+          <dt>port (q)</dt>
+          <dd>A TCP or UDP port number. If this parameter is specified and the
+            account for that protocol also specifies a port, this parameter
+            should override that in the account.</dd>
+
+          <dt>password (s)</dt>
+          <dd>A password associated with the account.</dd>
+
+          <dt>require-encryption (b)</dt>
+          <dd>Require encryption for this connection. A connection should fail
+            to connect if require-encryption is set and an encrypted connection
+            is not possible.</dd>
+
+          <dt>register (b)</dt>
+          <dd>This account should be created on the server if it does not
+            already exist.</dd>
+
+          <dt>ident (s)</dt>
+          <dd>The local username to report to the server if necessary, such as
+            in IRC.</dd>
+
+          <dt>fullname (s)</dt>
+          <dd>The user's full name if the service requires this when
+            authenticating or registering.</dd>
+
+          <dt>stun-server (s)</dt>
+          <dd>The IP address or FQDN of a STUN server to use for NAT traversal,
+            without any ":port" suffix.</dd>
+
+          <dt>stun-port (q)</dt>
+          <dd>The UDP port number on the stun-server to use for STUN. Only
+            significant if the stun-server is also supplied.</dd>
         </dl>
 
         <p>Every successful RequestConnection call will cause the emission of a
-- 
1.5.6.5