Minor clarification.

2 files changed, 9 insertions, 7 deletions

diff --git a/lispref/functions.texi b/lispref/functions.texi
index fa45e9ef11d..9f684593a98 100644
--- a/lispref/functions.texi
+++ b/lispref/functions.texi
@@ -364,9 +364,11 @@ is @code{nil}.
   There is no way to have required arguments following optional
 ones---it would not make sense.  To see why this must be so, suppose
 that @code{c} in the example were optional and @code{d} were required.
-Suppose three actual arguments are given; which variable would the third
-argument be for?  Similarly, it makes no sense to have any more
-arguments (either required or optional) after a @code{&rest} argument.
+Suppose three actual arguments are given; which variable would the
+third argument be for?  Would it be used for the @var{c}, or for
+@var{d}?  One can argue for both possibilities.  Similarly, it makes
+no sense to have any more arguments (either required or optional)
+after a @code{&rest} argument.
 
   Here are some examples of argument lists and proper calls:
 
diff --git a/lispref/text.texi b/lispref/text.texi
index 1cd8c14a85a..7129aa531e4 100644
--- a/lispref/text.texi
+++ b/lispref/text.texi
@@ -3513,10 +3513,10 @@ all markers unrelocated.
 @section Base 64 Encoding
 @cindex base 64 encoding
 
-  Base 64 code is used in email to encode a sequence of 8-bit bytes as a
-longer sequence of @sc{ascii} graphic characters.  It is defined in RFC
-2045.  This section describes the functions for converting to and from
-this code.
+  Base 64 code is used in email to encode a sequence of 8-bit bytes as
+a longer sequence of @sc{ascii} graphic characters.  It is defined in
+Internet RFC 2045.  This section describes the functions for
+converting to and from this code.
 
 @defun base64-encode-region beg end &optional no-line-break
 @tindex base64-encode-region