* NEWS (2.3a+): In the %code entry, reference section `Bison

[bison.git] / doc / bison.texinfo

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index c226a077a6e3335624b255141ec11c9cddbcddee..55a7759a2355080cdd2b8a03904587beb12cb4f0 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -2956,6 +2956,8 @@ type:
 You could even place each of the above directive groups in the rules section of
 the grammar file next to the set of rules that uses the associated semantic
 type.
+(In the rules section, you must terminate each of those directives with a
+semicolon.)
 And you don't have to worry that some directive (like a @code{%union}) in the
 definitions section is going to adversely affect their functionality in some
 counter-intuitive manner just because it comes first.
@@ -4396,7 +4398,7 @@ The parser can @dfn{return immediately} because of an explicit call to
 @code{YYABORT} or @code{YYACCEPT}, or failed error recovery, or memory
 exhaustion.
 
-Right-hand size symbols of a rule that explicitly triggers a syntax
+Right-hand side symbols of a rule that explicitly triggers a syntax
 error via @code{YYERROR} are not discarded automatically.  As a rule
 of thumb, destructors are invoked only when user actions cannot manage
 the memory.
@@ -8617,7 +8619,7 @@ The field's type can be changed using @samp{%define "stype"
 
 The different structure of the Java language forces several differences
 between C/C++ grammars, and grammars designed for Java parsers.  This
-section summarizes this differences.
+section summarizes these differences.
 
 @itemize
 @item
@@ -8650,7 +8652,7 @@ blocks, if specified, should include the implementation of the
 scanner.  If there is no such block, the scanner can be any class
 that implements the appropriate interface (see @pxref{Java Scanner
 Interface}).
-@end item
+@end table
 
 Other @code{%code} blocks are not supported in Java parsers.
 The epilogue has the same meaning as in C/C++ code and it can