(Client-Server Dialog): Markup fixes.

(Future changes): Markup fixes.

doc/Protocol-A.texi

@@ -2,8 +2,6 @@
 @c
 @c FIXME: Things ceder are about to fix:
 @c FIXME: 
-@c FIXME: move "Error Codes" and "Special Errors" into "Client-Server Dialog"
-@c FIXME: error-reply defined twice (conflicting).
 @c FIXME: sentence-end-double-space!
 @c FIXME: "Foo bar (bar baz.)" or "Foo bar (bar baz)."?
 @c FIXME: split "LysKOM Data Types"
@@ -24,7 +22,7 @@
 @c FIXME: "Review the last N by FOO to BAR" is empty
 @c FIXME: "Remote control" contains no information
 @c
-@c $Id: Protocol-A.texi,v 1.140 2001/05/05 07:38:55 ceder Exp $
+@c $Id: Protocol-A.texi,v 1.141 2001/05/05 08:28:13 ceder Exp $
 @c %**start of header
 @setfilename protocol-a.info
 @settitle LysKOM Protocol A
@@ -1370,13 +1368,13 @@ spaces and terminating all requests with a linefeed character.  The
 unless the client follows this requirement.
 
 The server may return two different types of errors. Normal
-@type{error-reply} errors are replies to syntactically correct calls
-to the server, while @type{protocol-error} are replies to syntactically
+@code{error-reply} errors are replies to syntactically correct calls
+to the server, while @code{protocol-error} are replies to syntactically
 incorrect calls.  @xref{Protocol Error Messages}, for more information
-about @type{protocol-error}.
+about @code{protocol-error}.
 
 If a call cannot complete successfully, LysKOM will respond with an
-@type{error-reply}.  The meaning of @field{error-code} and
+@code{error-reply}.  The meaning of @field{error-code} and
 @field{error-status} varies depending on the request; see @ref{Error
 Codes}, and the documentation for each call, for a list of available
 @field{error-code} values and what they mean.
@@ -9052,11 +9050,11 @@ read texts.
 @item
 The @reqlink{mark-as-read} call is a reasonably good way to mark a
 single text as read (but one could argue that it should take a single
-@type{Text-No} and an @type{ARRAY Conf-No} as arguments), but there is
+@code{Text-No} and an @code{ARRAY Conf-No} as arguments), but there is
 no easy way to undo such an operation.  You can use
 @reqlink{set-last-read} followed by a number of @req{mark-as-read}
 calls to get the desired effect, but it would be nice to have a
-@samp{mark-as-unread} call.
+@code{mark-as-unread} call.
 
 @item
 If the client issues several request without waiting for a reply, the