Use the new RFC macros wherever RFCs are referenced by number. No other

changes.

1 files changed, 6 insertions, 4 deletions

diff --git a/Doc/lib/libmailcap.tex b/Doc/lib/libmailcap.tex
index 2cbffa1..e1168ec 100644
--- a/Doc/lib/libmailcap.tex
+++ b/Doc/lib/libmailcap.tex
@@ -1,5 +1,6 @@
 \section{Standard Module \sectcode{mailcap}}
 \label{module-mailcap}
+\rfcindex{1524}
 \stmodindex{mailcap}
 \renewcommand{\indexsubitem}{(in module mailcap)}
 
@@ -12,7 +13,7 @@ message or Web document with the MIME type video/mpeg, \code{\%s} will be
 replaced by a filename (usually one belonging to a temporary file) and
 the xmpeg program can be automatically started to view the file.
 
-The mailcap format is documented in RFC 1524, ``A User Agent
+The mailcap format is documented in \rfc{1524}, ``A User Agent
 Configuration Mechanism For Multimedia Mail Format Information'', but
 is not an Internet standard.  However, mailcap files are supported on
 most \UNIX{} systems.
@@ -24,12 +25,13 @@ line to be executed
 the mailcap entry for a given MIME type.  If no matching MIME
 type can be found, \code{(None, None)} is returned.
 
-\var{key} is the name of the field desired, which represents the type of
-activity to be performed; the default value is 'view', since in the
+\var{key} is the name of the field desired, which represents the type
+of activity to be performed; the default value is 'view', since in the 
 most common case you simply want to view the body of the MIME-typed
 data.  Other possible values might be 'compose' and 'edit', if you
 wanted to create a new body of the given MIME type or alter the
-existing body data.  See RFC1524 for a complete list of these fields.
+existing body data.  See \rfc{1524} for a complete list of these
+fields.
 
 \var{filename} is the filename to be substituted for \%s in the
 command line; the default value is