(How Can I Reset the Parser): Renamed from `How Can I Reset

@code{yyparse}', since texinfo does not allow arbitrary @ in node
names.

diff --git a/doc/bison.texinfo b/doc/bison.texinfo
index d09f42a881a311273c4b2d6d876afac174449655..7cb1ae5a91c1ed30cea5c90569e6198d0568a421 100644 (file)
--- a/doc/bison.texinfo
+++ b/doc/bison.texinfo
@@ -284,7 +284,7 @@ Invoking Bison
 Frequently Asked Questions
 
 * Parser Stack Overflow::      Breaking the Stack Limits
-* How Can I Reset @code{yyparse}::    @code{yyparse} Keeps some State
+* How Can I Reset the Parser:: @code{yyparse} Keeps some State
 * Strings are Destroyed::      @code{yylval} Loses Track of Strings
 * C++ Parsers::                Compiling Parsers with C++ Compilers
 * Implementing Loops::         Control Flow in the Calculator
@@ -6356,7 +6356,7 @@ are addressed.
 
 @menu
 * Parser Stack Overflow::      Breaking the Stack Limits
-* How Can I Reset @code{yyparse}::    @code{yyparse} Keeps some State
+* How Can I Reset the Parser:: @code{yyparse} Keeps some State
 * Strings are Destroyed::      @code{yylval} Loses Track of Strings
 * C++ Parsers::                Compiling Parsers with C++ Compilers
 * Implementing Loops::         Control Flow in the Calculator
@@ -6373,8 +6373,8 @@ message.  What can I do?
 This question is already addressed elsewhere, @xref{Recursion,
 ,Recursive Rules}.
 
-@node How Can I Reset @code{yyparse}
-@section How Can I Reset @code{yyparse}
+@node How Can I Reset the Parser
+@section How Can I Reset the Parser
 
 The following phenomenon has several symptoms, resulting in the
 following typical questions: