(Client-Server Dialog): Document the format of the hello string. Fix

	the example.
(What do I have unread): Recommend that clients use get-uconf-stat
	instead of get-conf-stat.

doc/Protocol-A.texi

@@ -2,7 +2,7 @@
 @c
 @c FIXME: Explain how the garb works with nice and keep-commented
 @c
-@c $Id: Protocol-A.texi,v 1.103 2000/09/06 19:39:17 ceder Exp $
+@c $Id: Protocol-A.texi,v 1.104 2001/04/10 09:10:19 ceder Exp $
 @c %**start of header
 @setfilename protocol-a.info
 @settitle LysKOM Protocol A
@@ -1467,6 +1467,8 @@ followed by connection information required by that protocol. In
 protocol A the connection information is a Hollerith string saying who
 the user connecting is followed by a newline character.
 
+The format of the string should be @var{username} % @var{hostname}.
+
 When the server has accepted the connection its reply is
 protocol-dependent. Protocol A servers will reply with the string
 @code{LysKOM} on a single line if the connection attampt is successful.
@@ -1476,7 +1478,7 @@ protocol-dependent. Protocol A servers will reply with the string
         Trying 130.236.254.151 ...
         Connected to varg.lysator.liu.se.
         Escape character is '^]'.
-        A5Hbyers
+        A26Hbyers%kajsa.lysator.liu.se
         LysKOM
 @end example
 
@@ -8704,7 +8706,7 @@ an unread text.
 the previous step. This will return the membership data for all the
 conferences that may contain unread texts.
 
-@item Call @code{get-conf-stat} for each conference returned in
+@item Call @code{get-uconf-stat} for each conference returned in
 the first step. The conference status will be needed shortly. Repeat the 
 following steps for each conference.