Documentation: Consistently use "backtick" for `

diff --git a/doc/manual.xml.head b/doc/manual.xml.head
index e86512409c5c7748ccaa6aab2e9b2fec2db6b197..beb1afbefb399403809f34b564f88006c0decad2 100644 (file)
--- a/doc/manual.xml.head
+++ b/doc/manual.xml.head
@@ -1471,7 +1471,7 @@ middle of command names.
 <para>
 It is also possible to substitute the output of a Unix command in an
 initialization file.  This is accomplished by enclosing the command in
-backquotes (``).  For example,
+backticks (``).  For example,
 
 <screen>
 my_hdr X-Operating-System: `uname -a`

diff --git a/doc/muttrc.man.head b/doc/muttrc.man.head
index 5e46332e8a8952b96db5cd6d5adb474dfeb03c72..529f5735c81d696596cbd7d9f3b70b52c3aae4f7 100644 (file)
--- a/doc/muttrc.man.head
+++ b/doc/muttrc.man.head
@@ -40,7 +40,7 @@ similar to that of many popular shell programs, namely that a single
 quote is used to specify a literal string (one that is not
 interpreted for shell variables or quoting with a backslash [see
 next paragraph]), while double quotes indicate a string which
-should be evaluated.  For example, backquotes are evaluated inside of
+should be evaluated.  For example, backticks are evaluated inside of
 double quotes, but not single quotes.
 .PP
 \fB\(rs\fP quotes the next character, just as in shells such as bash and zsh.
@@ -58,7 +58,7 @@ middle of command names.
 .PP
 It is also possible to substitute the output of a Unix command in an
 initialization file.  This is accomplished by enclosing the command
-in backquotes (\fB`\fP\fIcommand\fP\fB`\fP).
+in backticks (\fB`\fP\fIcommand\fP\fB`\fP).
 .PP
 UNIX environment variables can be accessed like the way it is done in shells
 like sh and bash: Prepend the name of the variable by a dollar