Minor documentation update

doc/Protocol-A.texi

 \input texinfo                         @c -*-texinfo-*-
-@c $Id: Protocol-A.texi,v 1.45 1998/12/29 10:55:32 byers Exp $
+@c $Id: Protocol-A.texi,v 1.46 1998/12/29 13:18:45 byers Exp $
 @c %**start of header
 @setfilename protocol-a.info
 @settitle LysKOM Protocol A
@@ -825,6 +825,7 @@ Once created an item of this type cannot be deleted.
 
 
 @item redirect [8] (conference)
+
 This item indicates that texts should not be sent to the conference,
 but be directed to some other target instead. Clients should notify
 users that attempt to send texts to the conference of the redirect and
@@ -842,6 +843,7 @@ a mailbox, the person attached to the mailbox. The hide-creator and
 secret bits are cleared automatically. Only one redirect can be
 specified.
 
+
 @item x-face [9] (conference)
 
 Data is the face of the person in compface format. Cool, innit?
@@ -7280,11 +7282,11 @@ Login required before issuing this call.
 
 Asynchronous messages are information messages sent from the server to
 the client. Clients can select which messages to receive by issuing an
-@code{@ref{accept-async}} call. They can find out which messages are
-being sent by issuing the @code{@ref{query-async}} call. Note that the
-server can send other messages as well. For example, a broadcast message
-from a person with admin bits set may get through even if the client has
-not requests broadcast messages.
+@pxref{accept-async} call. They can find out which messages are being
+sent by issuing the @pxref{query-async} call. Note that the server can
+send other messages as well. For example, a broadcast message from a
+person with admin bits set may get through even if the client has not
+requests broadcast messages.
 
 When a connection is opened some messages are selected by default.
 Clients should use the @code{@ref{accept-async}} call to select which