NEWS 2.5 fixes

[Joel E. Denny]

I pushed these to branch-2.5 and master.

>From ac3297d501e9b74a11095d966bb8e5aa6fcf0ff4 Mon Sep 17 00:00:00 2001
From: Joel E. Denny <address@hidden>
Date: Sun, 1 May 2011 10:22:39 -0400
Subject: [PATCH 1/2] doc: clean up quotation style in NEWS.

* NEWS (2.5): For multi-character tokens in example grammar rules,
use "token" not 'token'.  In English, use a consistent quotation
style; we might as well follow the precedent seen in info pages:
`quote' not "quote".
---
 ChangeLog |    8 ++++++++
 NEWS      |   22 +++++++++++-----------
 2 files changed, 19 insertions(+), 11 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 243ee1f..2f77463 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,11 @@
+2011-05-01  Joel E. Denny  <address@hidden>
+
+       doc: clean up quotation style in NEWS.
+       * NEWS (2.5): For multi-character tokens in example grammar rules,
+       use "token" not 'token'.  In English, use a consistent quotation
+       style; we might as well follow the precedent seen in info pages:
+       `quote' not "quote".
+
 2011-04-16  Joel E. Denny  <address@hidden>
 
        tests: pacify gcc 4.6.0's -Wunused-but-set-variable.
diff --git a/NEWS b/NEWS
index 3d02e03..1b70a6a 100644
--- a/NEWS
+++ b/NEWS
@@ -21,12 +21,12 @@ Bison News
   When no ambiguity is possible, original symbol names may be used
   as named references:
 
-    if_stmt : 'if' cond_expr 'then' then_stmt ';'
+    if_stmt : "if" cond_expr "then" then_stmt ';'
     { $if_stmt = mk_if_stmt($cond_expr, $then_stmt); }
 
   In the more common case, explicit names may be declared:
 
-    stmt[res] : 'if' expr[cond] 'then' stmt[then] 'else' stmt[else] ';'
+    stmt[res] : "if" expr[cond] "then" stmt[then] "else" stmt[else] ';'
     { $res = mk_if_stmt($cond, $then, $else); }
 
   Location information is also accessible using @name syntax.  When
@@ -125,7 +125,7 @@ Bison News
   except that the manner in which Bison processes multiple definitions
   for the same NAME differs.  Most importantly, -F and --force-define
   quietly override %define, but -D and --define do not.  For further
-  details, see the section "Bison Options" in the Bison manual.
+  details, see the section `Bison Options' in the Bison manual.
 
 *** Variables renamed:
 
@@ -183,8 +183,8 @@ Bison News
 
   Similarly to the C parsers, the C++ parsers now define the YYRHSLOC
   macro and use it in the default YYLLOC_DEFAULT.  You are encouraged
-  to use it.  If, for instance, your location structure has "first"
-  and "last" members, instead of
+  to use it.  If, for instance, your location structure has `first'
+  and `last' members, instead of
 
       # define YYLLOC_DEFAULT(Current, Rhs, N)                             \
         do                                                                 \
@@ -266,7 +266,7 @@ Bison News
     in order to detect a syntax error.  Because no unexpected token or
     expected tokens can then be reported, the verbose syntax error
     message described above is suppressed, and the parser instead
-    reports the simpler message, "syntax error".  Previously, this
+    reports the simpler message, `syntax error'.  Previously, this
     suppression was sometimes erroneously triggered by %nonassoc when a
     lookahead was actually required.  Now verbose messages are
     suppressed only when all previous lookaheads have already been
@@ -302,7 +302,7 @@ Bison News
 
 ** -W/--warnings fixes:
 
-*** Bison now properly recognizes the "no-" versions of categories:
+*** Bison now properly recognizes the `no-' versions of categories:
 
   For example, given the following command line, Bison now enables all
   warnings except warnings for incompatibilities with POSIX Yacc:
@@ -313,7 +313,7 @@ Bison News
 
   Previously, conflict reports were independent of Bison's normal
   warning system.  Now, Bison recognizes the warning categories
-  "conflicts-sr" and "conflicts-rr".  This change has important
+  `conflicts-sr' and `conflicts-rr'.  This change has important
   consequences for the -W and --warnings command-line options.  For
   example:
 
@@ -327,16 +327,16 @@ Bison News
   expected number of conflicts is not reported, so -W and --warning
   then have no effect on the conflict report.
 
-*** The "none" category no longer disables a preceding "error":
+*** The `none' category no longer disables a preceding `error':
 
   For example, for the following command line, Bison now reports
   errors instead of warnings for incompatibilities with POSIX Yacc:
 
     bison -Werror,none,yacc gram.y
 
-*** The "none" category now disables all Bison warnings.
+*** The `none' category now disables all Bison warnings.
 
-  Previously, the "none" category disabled only Bison warnings for
+  Previously, the `none' category disabled only Bison warnings for
   which there existed a specific -W/--warning category.  However,
   given the following command line, Bison is now guaranteed to
   suppress all warnings:
-- 
1.7.0.4


>From 723206df6f4be135a708a4509ba99da5a256224e Mon Sep 17 00:00:00 2001
From: Joel E. Denny <address@hidden>
Date: Sun, 1 May 2011 17:33:14 -0400
Subject: [PATCH 2/2] * NEWS (2.5): Fix minor typos.

---
 ChangeLog |    4 ++++
 NEWS      |    4 ++--
 2 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 2f77463..d85b7fd 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,5 +1,9 @@
 2011-05-01  Joel E. Denny  <address@hidden>
 
+       * NEWS (2.5): Fix minor typos.
+
+2011-05-01  Joel E. Denny  <address@hidden>
+
        doc: clean up quotation style in NEWS.
        * NEWS (2.5): For multi-character tokens in example grammar rules,
        use "token" not 'token'.  In English, use a consistent quotation
diff --git a/NEWS b/NEWS
index 1b70a6a..3eb2cc6 100644
--- a/NEWS
+++ b/NEWS
@@ -40,7 +40,7 @@ Bison News
 
   IELR(1) is a minimal LR(1) parser table generation algorithm.  That
   is, given any context-free grammar, IELR(1) generates parser tables
-  with the full language recognition power of canonical LR(1) but with
+  with the full language-recognition power of canonical LR(1) but with
   nearly the same number of parser states as LALR(1).  This reduction
   in parser states is often an order of magnitude.  More importantly,
   because canonical LR(1)'s extra parser states may contain duplicate
@@ -142,7 +142,7 @@ Bison News
   The old names are now deprecated but will be maintained indefinitely
   for backward compatibility.
 
-*** Values no longer need to be quoted in grammar file:
+*** Values no longer need to be quoted in the grammar file:
 
   If a %define value is an identifier, it no longer needs to be placed
   within quotations marks.  For example,
-- 
1.7.0.4