Use YYFPRINTF instead of fprintf where appropriate. Reported by

[bison.git] / doc / bison.texinfo

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index 517a6455e3c783d5449f08da36edc6da21791f56..c39c325b7519f9baabd1b89b5a596c45e53540dd 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -4694,7 +4694,7 @@ already defined, so that the debugging facilities are compiled.
 @deffn {Directive} %define @var{variable}
 @deffnx {Directive} %define @var{variable} "@var{value}"
 Define a variable to adjust Bison's behavior.  The possible choices for
-@var{variable}, as well as their meanings, depends on the selected target
+@var{variable}, as well as their meanings, depend on the selected target
 language and/or the parser skeleton (@pxref{Decl Summary,,%language}).
 
 Some @var{variable}s may be used as boolean values: in this case, the
@@ -7236,7 +7236,7 @@ always possible.
 
 The trace facility outputs messages with macro calls of the form
 @code{YYFPRINTF (stderr, @var{format}, @var{args})} where
-@var{format} and @var{args} are the usual @code{printf} format and
+@var{format} and @var{args} are the usual @code{printf} format and variadic
 arguments.  If you define @code{YYDEBUG} to a nonzero value but do not
 define @code{YYFPRINTF}, @code{<stdio.h>} is automatically included
 and @code{YYFPRINTF} is defined to @code{fprintf}.