* doc/emacs/trouble.texi (Understanding Bug Reporting): Brevity.

ChangeLog fix.

2 files changed, 8 insertions, 8 deletions

diff --git a/doc/emacs/ChangeLog b/doc/emacs/ChangeLog
index 935ddf39272..4c931ce8cb8 100644
--- a/doc/emacs/ChangeLog
+++ b/doc/emacs/ChangeLog
@@ -1,3 +1,7 @@
+2013-12-28  Glenn Morris  <rgm@gnu.org>
+
+        * trouble.texi (Understanding Bug Reporting): Brevity.
+
 2013-12-27  Jarek Czekalski  <jarekczek@poczta.onet.pl>
 
         * mini.texi (Completion Options): Add a link to Shell Options.
@@ -5,8 +9,8 @@
         shell-completion-fignore from Shell Mode to Shell Options.
 
 2013-12-26  João Távora <joaotavora@gmail.com>
-        * emacs.texi (Matching): Describe new features of Electric Pair
-        mode.
+
+        * emacs.texi (Matching): Describe new features of Electric Pair mode.
 
 2013-12-25  Chong Yidong  <cyd@gnu.org>
 
diff --git a/doc/emacs/trouble.texi b/doc/emacs/trouble.texi
index 52fd77ed978..8c8968397d8 100644
--- a/doc/emacs/trouble.texi
+++ b/doc/emacs/trouble.texi
@@ -631,12 +631,8 @@ easily reproducible at all.  In that case, you should report what you
 have---but, as before, please stick to the raw facts about what you
 did to trigger the bug the first time.
 
-  Please do not stack multiple issues into one report unless it is
-really necessary.  For example, jamming @code{electric-indent-mode}
-and @code{electric-pair-mode} into one report, reporting multiple key
-binding problems into one report (e.g., @kbd{C-i} doesn't indent the
-current line, @code{M-h} doesn't set mark, etc.).  Please make one
-report for each individual problem.
+  If you have multiple issues that you want to report, please make a
+separate bug report for each.
 
 @node Checklist
 @subsection Checklist for Bug Reports