(LysKOM Content Types): Added markup for content types.

(Reformattable Text (text/x-kom-basic)): Ditto.
(Content type specification): Ditto.
(Document Edition History): Ditto.

doc/Protocol-A.texi

@@ -8680,8 +8680,8 @@ equivalent according to swascii rules.
 
 LysKOM defines a few special content types for texts.  They are all
 described in this chapter.  In addition to these, clients must support
-text/plain, should support text/enriched and are encouraged to support
-text/html.
+@samp{text/plain}, should support @samp{text/enriched} and are
+encouraged to support @samp{text/html}.
 
 @menu
 * Reformattable Text (text/x-kom-basic)::  
@@ -8691,7 +8691,8 @@ text/html.
 @node Reformattable Text (text/x-kom-basic)
 @section Reformattable Text
 
-This type of content corresponds to the mime type text/x-kom-basic.  It is raw
+This type of content corresponds to the mime type
+@samp{text/x-kom-basic}.  It is raw
 text that can be reformatted by the client without ill effects, but
 that can be legibly displayed on a text terminal without formatting.
 
@@ -8712,13 +8713,13 @@ that matched that regexp is to be prefixed to all lines of the
 paragraph.
 @end itemize
 
-This content type was previously erroneously called x-kom/basic, but
+This content type was previously erroneously called @samp{x-kom/basic}, but
 as far as we know no client ever created texts that were labeled with
-that name.  Please use the new name text/x-kom-basic instead.
+that name.  Please use the new name @samp{text/x-kom-basic} instead.
 
 Historical note: version 0.46.1 and earlier of the elisp client
-created texts labeled with x-kom/text.  Clients may treat that content
-type as as text/x-kom-basic for improved interoperability.
+created texts labeled with @samp{x-kom/text}.  Clients may treat that content
+type as as @samp{text/x-kom-basic} for improved interoperability.
 
 @node The User Area (x-kom/user-area)
 @section The User Area
@@ -9014,7 +9015,7 @@ The same conventions apply to messages sent with the
 This convention is understood by all popular clients.  If the first line
 is one of a few predefined strings, then this string specifies the type
 of text.  Currently only the strings ``html:'' and ``enriched:'' are
-supported, specifying text/html and text/enriched respectively.
+supported, specifying @samp{text/html} and @samp{text/enriched} respectively.
 
 Starting with protocol version 10, this ugly workaround is obsolete.  Use
 aux-items to specify content type instead.
@@ -9567,8 +9568,8 @@ Client Conventions appendix was written.  Distributed with lyskomd
 @item 10.4: 2001-05-24
 
 @emph{Fixed errors:}  Fixed the description of the @code{old-pwd} argument
-to @reqlink{set-passwd}.  The content-type x-kom/basic was renamed
-to text/x-kom-basic.
+to @reqlink{set-passwd}.  The content-type @samp{x-kom/basic} was renamed
+to @samp{text/x-kom-basic}.
 
 @emph{Previously undocumented stuff:}  Documented several previously
 undocumented aspects of the protocol: the hello string used during