summaryrefslogtreecommitdiff
path: root/doc/emacs/fixit.texi
diff options
context:
space:
mode:
authorPaul Eggert <eggert@cs.ucla.edu>2015-09-15 08:46:48 -0700
committerPaul Eggert <eggert@cs.ucla.edu>2015-09-15 08:48:44 -0700
commitef7dbdf5873bf0a1f3f0e64e5d019e74d5b15b9e (patch)
tree5b1d35e609ce4481816662709ac677db1468495b /doc/emacs/fixit.texi
parentc051487fcf379febf4ce5b38de7017609c84a106 (diff)
downloademacs-ef7dbdf5873bf0a1f3f0e64e5d019e74d5b15b9e.tar.gz
Quote less in manuals
The manuals often used quotes ``...'' when it is better to use @dfn or @code or capitalized words or no quoting at all. For example, there is no need for the `` and '' in “if a variable has one effect for @code{nil} values and another effect for ``non-@code{nil}'' values”. Reword the Emacs, Lisp intro, and Lisp reference manuals to eliminate unnecessary quoting like this, and to use @dfn etc. instead when called for (Bug#21472).
Diffstat (limited to 'doc/emacs/fixit.texi')
-rw-r--r--doc/emacs/fixit.texi4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/emacs/fixit.texi b/doc/emacs/fixit.texi
index 953b22f7d54..993f0dce1cc 100644
--- a/doc/emacs/fixit.texi
+++ b/doc/emacs/fixit.texi
@@ -286,7 +286,7 @@ messages. @xref{Sending Mail}.
When one of these commands encounters what appears to be an
incorrect word, it asks you what to do. It usually displays a list of
-numbered ``near-misses''---words that are close to the incorrect word.
+numbered @dfn{near-misses}---words that are close to the incorrect word.
Then you must type a single-character response. Here are the valid
responses:
@@ -331,7 +331,7 @@ file.
@item l @var{word} @key{RET}
Look in the dictionary for words that match @var{word}. These words
-become the new list of ``near-misses''; you can select one of them as
+become the new list of near-misses; you can select one of them as
the replacement by typing a digit. You can use @samp{*} in @var{word} as a
wildcard.