diff --git a/doc/Protocol-A.texi b/doc/Protocol-A.texi
index 864014437de87819dc52d64bda9e17648d4d6b2b..c20e2b62ada9f40a22a8fed4ec1c805c90f62813 100644
--- a/doc/Protocol-A.texi
+++ b/doc/Protocol-A.texi
@@ -1,5 +1,5 @@
 \input texinfo                         @c -*-texinfo-*-
-@c $Id: Protocol-A.texi,v 1.13 1998/08/08 15:36:07 ceder Exp $
+@c $Id: Protocol-A.texi,v 1.14 1998/08/08 21:46:20 ceder Exp $
 @c %**start of header
 @setfilename protocol-a.info
 @settitle LysKOM Protocol A
@@ -4516,7 +4516,7 @@ a single person. @code{person} is the person whose memberships are to be
 retrieved. @code{first} is the first position in the membership list to
 retrieve, numbered from 0 and up. @code{no-of-confs} is the number of
 membership records to retrieve. @code{mask} is a set of flags. Currently
-the only flag is @code{want-red-texts}, which instructs the server not
+the only flag is @code{want-read-texts}, which instructs the server not
 to send the @code{read-texts} array of the memberships.
 
 The server will return a membership list that is shorter than
@@ -5783,11 +5783,20 @@ when someone logs in (message 9).
 
 @unnumberedsubsubsec Error codes
 
+If the client requests a message that the server does not send, the
+server will reply with an error message saying which message number it
+does not support. The call will succeed anyway. This mechanism is useful
+for clients that want new versions of some messages, but need to be
+compatible with older servers.
+
 @table @code
 @item unknown-async
-One of the numbers in @code{request-list} is not the number of an async
-message the server knows about. The error-status indicates the index of
-the offending number.
+At least one of the numbers in @code{request-list} is not the number of
+an async message the server knows about. The error-status indicates the
+first offending number.
+
+Please note that a bug in lyskomd 1.9.0 prevented the server from
+sending this error message (frankly, we simply forgot about it.)
 @end table
 
 
@@ -5806,15 +5815,6 @@ messages that are not listed in the result of this call. Even though
 those messages are turned off, the server may decide to send them under
 certain circumstances.
 
-If the client requests a message that the server does not send, the
-server will reply with an error message saying which message number it
-does not support. The call will succeed anyway. This mechanism is useful
-for clients that want new versions of some messages, but need to be
-compatible with older servers.
-
-Please note that a bug in lyskomd 1.9.0 prevented the server from
-sending this error message (frankly, we simply forgot about it.)
-
 @i{Example:}
 @example
         1 81
@@ -6199,7 +6199,7 @@ The conference @code{conf-no} does not exist or is secret.
                 -> ( );
 @end example
 
-This call deleted the aux-items listed in @code{delete} from the text
+This call deletes the aux-items listed in @code{delete} from the text
 @code{text} and then adds the ones listed in @code{add} to the text.
 Either list may be empty, and the call is guaranteed to either
 completely fail or completely succeed.
@@ -6414,7 +6414,7 @@ a single person. @code{person} is the person whose memberships are to be
 retrieved. @code{first} is the first position in the membership list to
 retrieve, numbered from 0 and up. @code{no-of-confs} is the number of
 membership records to retrieve. @code{mask} is a set of flags. Currently
-the only flag is @code{want-red-texts}, which instructs the server not
+the only flag is @code{want-read-texts}, which instructs the server not
 to send the @code{read-texts} array of the memberships.
 
 The server will return a membership list that is shorter than