BUG-REPORT: Update quotation style.

	* BUG-REPORT: Migrate away from roff quotes (and TeX quotes);
	this is a plain-text document.

	Also fix bad wording: "you are used to compile groff" -> "you
	used to compile groff"; thanks to Dave Kemper for this fix.

Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>

1 files changed, 11 insertions, 11 deletions

diff --git a/BUG-REPORT b/BUG-REPORT
index bafde2992..dcf93c8b0 100644
--- a/BUG-REPORT
+++ b/BUG-REPORT
@@ -1,13 +1,13 @@
 # Copyright (C) 1999-2018 Free Software Foundation, Inc.
 #
-# This file is part of `groff'.
+# This file is part of 'groff'.
 #
-# `groff' is free software; you can redistribute it and/or modify it
+# 'groff' is free software; you can redistribute it and/or modify it
 # under the terms of the GNU General Public License as published by
 # the Free Software Foundation, either version 2 of the License, or
 # (at your option) any later version.
 #
-# `groff' is distributed in the hope that it will be useful, but
+# 'groff' is distributed in the hope that it will be useful, but
 # WITHOUT ANY WARRANTY; without even the implied warranty of
 # MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
 # General Public License for more details.
@@ -30,16 +30,16 @@ Please report separate bugs separately.
 Send the completed form to bug-groff@gnu.org
 
 GROFF VERSION:
-[The version of groff you are using.  For example, `1.05']
+[The version of groff you are using.  For example, '1.22.4']
 
 MACHINE:
-[The machine you are using.  For example, `Sun SPARCstation 2']
+[The machine you are using.  For example, 'Sun SPARCstation 2']
 
 OS:
-[The operating system you are using.  For example, `SunOS 4.1.1']
+[The operating system you are using.  For example, 'SunOS 4.1.1']
 
 COMPILER:
-[The compiler you are used to compile groff.  For example, `g++ 1.40.3']
+[The compiler you used to compile groff.  For example, 'g++ 1.40.3']
 
 INPUT FILES:
 [Include all the files necessary to reproduce the problem that are not
@@ -52,18 +52,18 @@ It's easier for us if you can provide an example that doesn't depend on
 any macro package, but obviously if you're reporting a problem with a
 macro package that won't be possible.  Also a short example is more
 convenient than a long one, but don't worry if you can't find a short
-example.  Don't say something like ``any file that X'': Always send a
+example.  Don't say something like "any file that X": Always include a
 definite example.]
 
 COMMAND LINE:
 [The command line that we should run in order to observe the bug.  For
-example, `gtroff -Tps bug.tr'.  If the command line uses -ms or -mm,
+example, 'gtroff -Tps bug.tr'.  If the command line uses -ms or -mm,
 say whether these refer to the groff versions or the Unix versions of
 the macros.]
 
 DESCRIPTION OF INCORRECT BEHAVIOUR:
-[What goes wrong when that command line is run?  For example, `gtroff
-gets a segmentation fault', or `The output looks bad because the bar
+[What goes wrong when that command line is run?  For example, 'gtroff
+gets a segmentation fault', or 'The output looks bad because the bar
 over the x is too long and is too far over to the left.'  If you get an
 error message, include it here without modification: Don't edit it to
 make it more readable.]