Restore some of the quoting in the manuals

* doc/lispref/windows.texi (Coordinates and Windows)
(Coordinates and Windows):
* doc/lispref/variables.texi (Lexical Binding)
(File Local Variables):
* doc/lispref/text.texi (Format Properties):
* doc/lispref/symbols.texi (Symbol Components):
* doc/lispref/strings.texi (Creating Strings):
* doc/lispref/sequences.texi (Sequence Functions):
* doc/lispref/searching.texi (Regexp Special, Regexp Search)
(Search and Replace):
* doc/lispref/processes.texi (Bindat Spec):
* doc/lispref/os.texi (Idle Timers):
* doc/lispref/objects.texi (Basic Char Syntax):
* doc/lispref/numbers.texi (Float Basics, Random Numbers):
* doc/lispref/nonascii.texi (Character Properties):
* doc/lispref/modes.texi (Major Mode Conventions, Mode Hooks)
(Mode Line Variables):
* doc/lispref/minibuf.texi (Text from Minibuffer):
* doc/lispref/loading.texi (Autoload):
* doc/lispref/keymaps.texi (Controlling Active Maps):
* doc/lispref/frames.texi (Frame Layout, Size and Position)
(Size Parameters, Implied Frame Resizing):
* doc/lispref/files.texi (Changing Files, Magic File Names):
* doc/lispref/eval.texi (Self-Evaluating Forms):
* doc/lispref/display.texi (Progress, Abstract Display)
(Abstract Display Example, Bidirectional Display):
* doc/lispref/commands.texi (Event Mod):
* doc/emacs/windows.texi (Displaying Buffers):
* doc/emacs/trouble.texi (Bug Criteria, Checklist):
* doc/emacs/text.texi (Enriched Text):
* doc/emacs/programs.texi (MixedCase Words):
* doc/emacs/picture-xtra.texi (Insert in Picture)
(Tabs in Picture):
* doc/emacs/misc.texi (Emacs Server, Printing):
* doc/emacs/mini.texi (Minibuffer History):
* doc/emacs/maintaining.texi (Old Revisions, VC Change Log)
(Pulling / Pushing):
* doc/emacs/killing.texi (Yanking, Cut and Paste, Clipboard):
* doc/emacs/help.texi (Help, Help Echo):
* doc/emacs/glossary.texi (Glossary):
* doc/emacs/frames.texi (Mouse Commands, Creating Frames)
(Frame Commands):
* doc/emacs/files.texi (Reverting, Saving, Directories):
* doc/emacs/entering.texi (Exiting):
* doc/emacs/emacs.texi (Top):
* doc/emacs/cmdargs.texi (Window Size X, Icons X):
* doc/emacs/anti.texi (Antinews): Restore quoting of text where
appropriate or replace quoting with @dfn.
* doc/misc/ediff.texi (Window and Frame Configuration):
* doc/lispref/processes.texi (Network Feature Testing):
* doc/lispref/display.texi (Display Margins): Quote the phrase
after "a.k.a." where appropriate.

22 files changed, 57 insertions, 56 deletions

diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 8642f6ae956..7ddf5ee8f74 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -2621,7 +2621,7 @@ then continues to wait for a valid input character, or keyboard-quit.
 from @code{read-event}.
 
 @defvar extra-keyboard-modifiers
-This variable lets Lisp programs press the modifier keys on the
+This variable lets Lisp programs ``press'' the modifier keys on the
 keyboard.  The value is a character.  Only the modifiers of the
 character matter.  Each time the user types a keyboard key, it is
 altered as if those modifier keys were held down.  For instance, if
diff --git a/doc/lispref/display.texi b/doc/lispref/display.texi
index 2ae2857afda..f3713bf15b0 100644
--- a/doc/lispref/display.texi
+++ b/doc/lispref/display.texi
@@ -386,7 +386,7 @@ results of @code{point-min} and @code{point-max} correspondingly.
 
 Alternatively, you can set @var{min-value} and @var{max-value} to
 @code{nil}.  In that case, the progress reporter does not report
-process percentages; it instead displays a spinner that rotates a
+process percentages; it instead displays a ``spinner'' that rotates a
 notch each time you update the progress reporter.
 
 If @var{min-value} and @var{max-value} are numbers, you can give the
@@ -4644,7 +4644,7 @@ variables:
 
 @defvar left-margin-width
 This variable specifies the width of the left margin, in character
-cell (a.k.a.@: column) units.  It is buffer-local in all buffers.
+cell (a.k.a.@: ``column'') units.  It is buffer-local in all buffers.
 A value of @code{nil} means no left marginal area.
 @end defvar
 
@@ -5883,8 +5883,8 @@ in the search, instead of starting at the next button.
 
   The Ewoc package constructs buffer text that represents a structure
 of Lisp objects, and updates the text to follow changes in that
-structure.  This is like the view component in the
-model--view--controller design paradigm.  Ewoc means ``Emacs's
+structure.  This is like the ``view'' component in the
+``model--view--controller'' design paradigm.  Ewoc means ``Emacs's
 Widget for Object Collections''.
 
   An @dfn{ewoc} is a structure that organizes information required to
@@ -6164,7 +6164,7 @@ The buffer is in Color Components mode."
 
 @cindex controller part, model/view/controller
   This example can be extended to be a color selection widget (in
-other words, the controller part of the model--view--controller
+other words, the ``controller'' part of the ``model--view--controller''
 design paradigm) by defining commands to modify @code{colorcomp-data}
 and to finish the selection process, and a keymap to tie it all
 together conveniently.
@@ -6822,9 +6822,9 @@ positions do not increase monotonically with string or buffer
 position.  In performing this @dfn{bidirectional reordering}, Emacs
 follows the Unicode Bidirectional Algorithm (a.k.a.@: @acronym{UBA}),
 which is described in Annex #9 of the Unicode standard
-(@url{http://www.unicode.org/reports/tr9/}).  Emacs provides a Full
-Bidirectionality class implementation of the @acronym{UBA},
-consistent with the requirements of the Unicode Standard v7.0.
+(@url{http://www.unicode.org/reports/tr9/}).  Emacs provides a ``Full
+Bidirectionality'' class implementation of the @acronym{UBA},
+consistent with the requirements of the Unicode Standard v8.0.
 
 @defvar bidi-display-reordering
 If the value of this buffer-local variable is non-@code{nil} (the
diff --git a/doc/lispref/eval.texi b/doc/lispref/eval.texi
index a7c44c66ec3..067dbd2d99f 100644
--- a/doc/lispref/eval.texi
+++ b/doc/lispref/eval.texi
@@ -146,7 +146,7 @@ contents unchanged.
      @result{} 123
 @end group
 @group
-(eval '123)        ; @r{Evaluated by hand---result is the same.}
+(eval '123)        ; @r{Evaluated "by hand"---result is the same.}
      @result{} 123
 @end group
 @group
diff --git a/doc/lispref/files.texi b/doc/lispref/files.texi
index 735e08eb324..ffc7936107b 100644
--- a/doc/lispref/files.texi
+++ b/doc/lispref/files.texi
@@ -1603,7 +1603,7 @@ file.  This works only on some operating systems, and only if you have
 the correct permissions to do so.
 
 If the optional argument @var{preserve-permissions} is non-@code{nil},
-this function copies the file modes (or permissions) of
+this function copies the file modes (or ``permissions'') of
 @var{oldname} to @var{newname}, as well as the Access Control List and
 SELinux context (if any).  @xref{Information about Files}.
 
@@ -2753,7 +2753,7 @@ no prefix argument is given, and @code{nil} otherwise.
 @end deffn
 
 @node Magic File Names
-@section Making Certain File Names Magic
+@section Making Certain File Names ``Magic''
 @cindex magic file names
 
   You can implement special handling for certain file names.  This is
diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index 473c8252b05..629ee5c5eca 100644
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -500,7 +500,7 @@ Position}).
 @cindex external border
 The @dfn{external border} is part of the decorations supplied by the
 window manager.  It's typically used for resizing the frame with the
-mouse.  The external border is normally not shown on fullboth and
+mouse.  The external border is normally not shown on ``fullboth'' and
 maximized frames (@pxref{Size Parameters}) and doesn't exist for text
 terminal frames.
 
@@ -841,7 +841,7 @@ of its character size, however, may: be ignored, cause a rounding
 (GTK+), or be accepted (Lucid, Motif, MS-Windows).
 
 With some window managers you may have to set this to non-@code{nil} in
-order to make a frame appear truly maximized or fullscreen.
+order to make a frame appear truly maximized or full-screen.
 @end defopt
 
 @defun set-frame-size frame width height pixelwise
@@ -914,7 +914,7 @@ resize the frame's outer size, hence this will alter the number of
 displayed lines.
 
    Occasionally, such @dfn{implied frame resizing} may be unwanted, for
-example, when the frame is maximized or made fullscreen (where it's
+example, when the frame is maximized or made full-screen (where it's
 turned off by default).  In other cases you can disable implied resizing
 with the following option:
 
@@ -1288,34 +1288,34 @@ or both.  Its value can be @code{fullwidth}, @code{fullheight},
 @code{fullboth}, or @code{maximized}.  A @dfn{fullwidth} frame is as
 wide as possible, a @dfn{fullheight} frame is as tall as possible, and
 a @dfn{fullboth} frame is both as wide and as tall as possible.  A
-@dfn{maximized} frame is like a fullboth frame, except that it usually
+@dfn{maximized} frame is like a ``fullboth'' frame, except that it usually
 keeps its title bar and the buttons for resizing
 and closing the frame.  Also, maximized frames typically avoid hiding
-any task bar or panels displayed on the desktop.  A fullboth frame,
+any task bar or panels displayed on the desktop.  A ``fullboth'' frame,
 on the other hand, usually omits the title bar and occupies the entire
 available screen space.
 
-Fullheight and fullwidth frames are more similar to maximized
+Full-height and full-width frames are more similar to maximized
 frames in this regard.  However, these typically display an external
 border which might be absent with maximized frames.  Hence the heights
-of maximized and fullheight frames and the widths of maximized and
-fullwidth frames often differ by a few pixels.
+of maximized and full-height frames and the widths of maximized and
+full-width frames often differ by a few pixels.
 
 With some window managers you may have to customize the variable
 @code{frame-resize-pixelwise} (@pxref{Size and Position}) in order to
-make a frame truly appear maximized or fullscreen.  Moreover,
+make a frame truly appear maximized or full-screen.  Moreover,
 some window managers might not support smooth transition between the
-various fullscreen or maximization states.  Customizing the variable
+various full-screen or maximization states.  Customizing the variable
 @code{x-frame-normalize-before-maximize} can help to overcome that.
 
 @vindex fullscreen-restore, a frame parameter
 @item fullscreen-restore
 This parameter specifies the desired fullscreen state of the frame
 after invoking the @code{toggle-frame-fullscreen} command (@pxref{Frame
-Commands,,, emacs, The GNU Emacs Manual}) in the fullboth state.
+Commands,,, emacs, The GNU Emacs Manual}) in the ``fullboth'' state.
 Normally this parameter is installed automatically by that command when
 toggling the state to fullboth.  If, however, you start Emacs in the
-fullboth state, you have to specify the desired behavior in your initial
+``fullboth'' state, you have to specify the desired behavior in your initial
 file as, for example
 
 @example
diff --git a/doc/lispref/keymaps.texi b/doc/lispref/keymaps.texi
index d665587dbf3..9bea4b0af1c 100644
--- a/doc/lispref/keymaps.texi
+++ b/doc/lispref/keymaps.texi
@@ -929,7 +929,7 @@ sequences entered using the menu bar, even if they do not affect the
 menu bar display.  So if a menu bar key sequence comes in, you should
 clear the variables before looking up and executing that key sequence.
 Modes that use the variables would typically do this anyway; normally
-they respond to events that they do not handle by unreading them and
+they respond to events that they do not handle by ``unreading'' them and
 exiting.
 @end defvar
 
diff --git a/doc/lispref/loading.texi b/doc/lispref/loading.texi
index f5352da59f7..82de765876e 100644
--- a/doc/lispref/loading.texi
+++ b/doc/lispref/loading.texi
@@ -456,7 +456,7 @@ Autoloading can also be triggered by looking up the documentation of
 the function or macro (@pxref{Documentation Basics}).
 
   There are two ways to set up an autoloaded function: by calling
-@code{autoload}, and by writing a magic comment in the
+@code{autoload}, and by writing a ``magic'' comment in the
 source before the real definition.  @code{autoload} is the low-level
 primitive for autoloading; any Lisp program can call @code{autoload} at
 any time.  Magic comments are the most convenient way to make a function
diff --git a/doc/lispref/minibuf.texi b/doc/lispref/minibuf.texi
index a035459abdb..96c1020d748 100644
--- a/doc/lispref/minibuf.texi
+++ b/doc/lispref/minibuf.texi
@@ -143,7 +143,7 @@ reads the text and returns the resulting Lisp object, unevaluated.
 The argument @var{default} specifies default values to make available
 through the history commands.  It should be a string, a list of
 strings, or @code{nil}.  The string or strings become the minibuffer's
-future history, available to the user with @kbd{M-n}.
+``future history'', available to the user with @kbd{M-n}.
 
 If @var{read} is non-@code{nil}, then @var{default} is also used
 as the input to @code{read}, if the user enters empty input.
@@ -194,8 +194,8 @@ in @code{read-from-minibuffer} it should be a string, a list of
 strings, or @code{nil}, which is equivalent to an empty string.  When
 @var{default} is a string, that string is the default value.  When it
 is a list of strings, the first string is the default value.  (All
-these strings are available to the user in the future minibuffer
-history.)
+these strings are available to the user in the ``future minibuffer
+history''.)
 
 This function works by calling the
 @code{read-from-minibuffer} function:
@@ -262,8 +262,8 @@ The last string or pattern used in query-replace commands.
 The function now has a list of regular expressions that it passes to
 @code{read-from-minibuffer} to obtain the user's input.  The first
 element of the list is the default result in case of empty input.  All
-elements of the list are available to the user as the future
-minibuffer history list (@pxref{Minibuffer History, future list,,
+elements of the list are available to the user as the ``future
+minibuffer history'' list (@pxref{Minibuffer History, future list,,
 emacs, The GNU Emacs Manual}).
 
 The optional argument @var{history}, if non-@code{nil}, is a symbol
diff --git a/doc/lispref/modes.texi b/doc/lispref/modes.texi
index cbc8b78a0e8..8d7e29f9eef 100644
--- a/doc/lispref/modes.texi
+++ b/doc/lispref/modes.texi
@@ -305,7 +305,7 @@ which documentation to print.
 
 @item
 The major mode command should set the variable @code{mode-name} to the
-pretty name of the mode, usually a string (but see @ref{Mode Line
+``pretty'' name of the mode, usually a string (but see @ref{Mode Line
 Data}, for other possible forms).  The name of the mode appears
 in the mode line.
 
@@ -901,7 +901,7 @@ such a major mode, please correct it to follow these conventions.
 
   When you defined a major mode using @code{define-derived-mode}, it
 automatically makes sure these conventions are followed.  If you
-define a major mode by hand, not using @code{define-derived-mode},
+define a major mode ``by hand'', not using @code{define-derived-mode},
 use the following functions to handle these conventions automatically.
 
 @defun run-mode-hooks &rest hookvars
@@ -1974,7 +1974,7 @@ This variable is used to identify @code{emacsclient} frames.
   The following three variables are used in @code{mode-line-modes}:
 
 @defvar mode-name
-This buffer-local variable holds the pretty name of the current
+This buffer-local variable holds the ``pretty'' name of the current
 buffer's major mode.  Each major mode should set this variable so that
 the mode name will appear in the mode line.  The value does not have
 to be a string, but can use any of the data types valid in a mode-line
diff --git a/doc/lispref/nonascii.texi b/doc/lispref/nonascii.texi
index 99d128c0535..fb76de1ca09 100644
--- a/doc/lispref/nonascii.texi
+++ b/doc/lispref/nonascii.texi
@@ -483,7 +483,7 @@ Corresponds to the Unicode @code{Numeric_Value} property for
 characters whose @code{Numeric_Type} is @samp{Decimal}.  The value is
 an integer, or @code{nil} if the character has no decimal digit value.
 For unassigned codepoints, the value is @code{nil}, which means
-@acronym{NaN}, or not a number.
+@acronym{NaN}, or ``not a number''.
 
 @item digit-value
 Corresponds to the Unicode @code{Numeric_Value} property for
diff --git a/doc/lispref/numbers.texi b/doc/lispref/numbers.texi
index b329a10b084..3c70d2f0a06 100644
--- a/doc/lispref/numbers.texi
+++ b/doc/lispref/numbers.texi
@@ -224,7 +224,7 @@ distinguish them.
 @cindex NaN
   The @acronym{IEEE} floating-point standard supports positive
 infinity and negative infinity as floating-point values.  It also
-provides for a class of values called NaN or not a number;
+provides for a class of values called NaN, or ``not a number'';
 numerical functions return such values in cases where there is no
 correct answer.  For example, @code{(/ 0.0 0.0)} returns a NaN@.
 Although NaN values carry a sign, for practical purposes there is no other
@@ -1217,7 +1217,8 @@ fashion.  The numbers are not truly random, but they have certain
 properties that mimic a random series.  For example, all possible
 values occur equally often in a pseudo-random series.
 
-  Pseudo-random numbers are generated from a seed.  Starting from
+@cindex seed, for random number generation
+  Pseudo-random numbers are generated from a @dfn{seed value}.  Starting from
 any given seed, the @code{random} function always generates the same
 sequence of numbers.  By default, Emacs initializes the random seed at
 startup, in such a way that the sequence of values of @code{random}
diff --git a/doc/lispref/objects.texi b/doc/lispref/objects.texi
index 4a0ccc86561..0a19274f6a1 100644
--- a/doc/lispref/objects.texi
+++ b/doc/lispref/objects.texi
@@ -310,7 +310,7 @@ vertical tab, formfeed, space, return, del, and escape as @samp{?\a},
 @samp{?\b}, @samp{?\t}, @samp{?\n}, @samp{?\v}, @samp{?\f},
 @samp{?\s}, @samp{?\r}, @samp{?\d}, and @samp{?\e}, respectively.
 (@samp{?\s} followed by a dash has a different meaning---it applies
-the super modifier to the following character.)  Thus,
+the Super modifier to the following character.)  Thus,
 
 @example
 ?\a @result{} 7                 ; @r{control-g, @kbd{C-g}}
diff --git a/doc/lispref/os.texi b/doc/lispref/os.texi
index ca4b1f07403..cb583038979 100644
--- a/doc/lispref/os.texi
+++ b/doc/lispref/os.texi
@@ -1922,7 +1922,7 @@ This is a convenient way to test whether Emacs is idle.
 @end defun
 
   The main use of @code{current-idle-time} is when an idle timer
-function wants to take a break for a while.  It can set up another
+function wants to ``take a break'' for a while.  It can set up another
 idle timer to call the same function again, after a few seconds more
 idleness.  Here's an example:
 
diff --git a/doc/lispref/positions.texi b/doc/lispref/positions.texi
index 75b29c1d395..92f98ab890f 100644
--- a/doc/lispref/positions.texi
+++ b/doc/lispref/positions.texi
@@ -409,7 +409,7 @@ mentioned here only for completeness.
 @deffn Command previous-line count
 @cindex goal column
 This function moves point up @var{count} lines (down if @var{count}
-is negative).  In moving, it attempts to keep point in the goal column
+is negative).  In moving, it attempts to keep point in the @dfn{goal column}
 (normally the same column that it was at the beginning of the move).
 
 If there is no character in the target line exactly under the current
diff --git a/doc/lispref/processes.texi b/doc/lispref/processes.texi
index a62a8b6b4ad..845db0df1ac 100644
--- a/doc/lispref/processes.texi
+++ b/doc/lispref/processes.texi
@@ -2538,7 +2538,7 @@ Non-@code{nil} if non-blocking connect is supported.
 @item (:type datagram)
 Non-@code{nil} if datagrams are supported.
 @item (:family local)
-Non-@code{nil} if local (a.k.a.@: UNIX domain) sockets are supported.
+Non-@code{nil} if local (a.k.a.@: ``UNIX domain'') sockets are supported.
 @item (:family ipv6)
 Non-@code{nil} if IPv6 is supported.
 @item (:service t)
@@ -2837,8 +2837,8 @@ is automatically recognized as risky.
   A field's @dfn{type} describes the size (in bytes) of the object
 that the field represents and, in the case of multibyte fields, how
 the bytes are ordered within the field.  The two possible orderings
-are big endian (also known as network byte ordering) and
-little endian.  For instance, the number @code{#x23cd} (decimal
+are @dfn{big endian} (also known as ``network byte ordering'') and
+@dfn{little endian}.  For instance, the number @code{#x23cd} (decimal
 9165) in big endian would be the two bytes @code{#x23} @code{#xcd};
 and in little endian, @code{#xcd} @code{#x23}.  Here are the possible
 type values:
diff --git a/doc/lispref/searching.texi b/doc/lispref/searching.texi
index 6dc4a16c765..adaf43159af 100644
--- a/doc/lispref/searching.texi
+++ b/doc/lispref/searching.texi
@@ -359,7 +359,7 @@ preceding expression either once or not at all.  For example,
 
 @item @samp{*?}, @samp{+?}, @samp{??}
 @cindex non-greedy repetition characters in regexp
-These are non-greedy variants of the operators @samp{*}, @samp{+}
+These are @dfn{non-greedy} variants of the operators @samp{*}, @samp{+}
 and @samp{?}.  Where those operators match the largest possible
 substring (consistent with matching the entire containing expression),
 the non-greedy variants match the smallest possible substring
@@ -1127,7 +1127,7 @@ avoids modifying the match data.
 @defun looking-at regexp
 This function determines whether the text in the current buffer directly
 following point matches the regular expression @var{regexp}.  ``Directly
-following'' means precisely that: the search is anchored and it can
+following'' means precisely that: the search is ``anchored'' and it can
 succeed only starting with the first character following point.  The
 result is @code{t} if so, @code{nil} otherwise.
 
@@ -1766,7 +1766,7 @@ to the functions that use this map.
 Prefix keys are not supported; each key binding must be for a
 single-event key sequence.  This is because the functions don't use
 @code{read-key-sequence} to get the input; instead, they read a single
-event and look it up by hand.
+event and look it up ``by hand''.
 @end itemize
 @end defvar
 
diff --git a/doc/lispref/sequences.texi b/doc/lispref/sequences.texi
index f38aa350963..6292c02a21d 100644
--- a/doc/lispref/sequences.texi
+++ b/doc/lispref/sequences.texi
@@ -342,7 +342,7 @@ order elements according to different criteria.
 The argument @var{predicate} must be a function that accepts two
 arguments.  It is called with two elements of @var{sequence}.  To get an
 increasing order sort, the @var{predicate} should return non-@code{nil} if the
-first element is less than the second, or @code{nil} if not.
+first element is ``less'' than the second, or @code{nil} if not.
 
 The comparison function @var{predicate} must give reliable results for
 any given pair of arguments, at least within a single call to
diff --git a/doc/lispref/strings.texi b/doc/lispref/strings.texi
index b2fe60c93cc..ac11dd9880f 100644
--- a/doc/lispref/strings.texi
+++ b/doc/lispref/strings.texi
@@ -343,7 +343,7 @@ three previous examples are rarely relevant:
 @end example
 
 Somewhat odd, but predictable, behavior can occur for certain
-non-greedy values of @var{separators} that can prefer empty
+``non-greedy'' values of @var{separators} that can prefer empty
 matches over non-empty matches.  Again, such values rarely occur in
 practice:
 
diff --git a/doc/lispref/symbols.texi b/doc/lispref/symbols.texi
index e6dc4df629e..2605a3e7b5a 100644
--- a/doc/lispref/symbols.texi
+++ b/doc/lispref/symbols.texi
@@ -35,7 +35,7 @@ otherwise.
 @section Symbol Components
 @cindex symbol components
 
-  Each symbol has four components (or cells), each of which
+  Each symbol has four components (or ``cells''), each of which
 references another object:
 
 @table @asis
diff --git a/doc/lispref/text.texi b/doc/lispref/text.texi
index 45e923218d7..6d9d26f0ad1 100644
--- a/doc/lispref/text.texi
+++ b/doc/lispref/text.texi
@@ -3487,7 +3487,7 @@ are used for representing formatted text.  @xref{Filling}, and
 
 @table @code
 @item hard
-If a newline character has this property, it is a hard newline.
+If a newline character has this property, it is a ``hard'' newline.
 The fill commands do not alter hard newlines and do not move words
 across them.  However, this property takes effect only if the
 @code{use-hard-newlines} minor mode is enabled.  @xref{Hard and Soft
diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi
index 76dc8e8a81e..1d920942d10 100644
--- a/doc/lispref/variables.texi
+++ b/doc/lispref/variables.texi
@@ -991,7 +991,7 @@ environments in this way; only specialized programs like debuggers.)
 @cindex closures, example of using
   Lexical bindings have indefinite extent.  Even after a binding
 construct has finished executing, its lexical environment can be
-kept around in Lisp objects called @dfn{closures}.  A closure is
+``kept around'' in Lisp objects called @dfn{closures}.  A closure is
 created when you define a named or anonymous function with lexical
 binding enabled.  @xref{Closures}, for details.
 
@@ -1722,7 +1722,7 @@ values by files.  Any value specified for one of these variables is
 completely ignored.
 @end defvar
 
-  The @samp{Eval:} variable is also a potential loophole, so Emacs
+  The @samp{Eval:} ``variable'' is also a potential loophole, so Emacs
 normally asks for confirmation before handling it.
 
 @defopt enable-local-eval
@@ -1735,7 +1735,7 @@ the user what to do for each file.  The default value is @code{maybe}.
 
 @defopt safe-local-eval-forms
 This variable holds a list of expressions that are safe to
-evaluate when found in the @samp{Eval:} variable in a file
+evaluate when found in the @samp{Eval:} ``variable'' in a file
 local variables list.
 @end defopt
 
diff --git a/doc/lispref/windows.texi b/doc/lispref/windows.texi
index 3479e180221..00161b28b66 100644
--- a/doc/lispref/windows.texi
+++ b/doc/lispref/windows.texi
@@ -3702,8 +3702,8 @@ respectively.
 
   For the following functions, X and Y coordinates are reported in
 integer character units, i.e., numbers of lines and columns
-respectively.  On a graphical display, each line and column
-corresponds to the height and width of a default character specified by
+respectively.  On a graphical display, each ``line'' and ``column''
+corresponds to the height and width of the default character specified by
 the frame's default font (@pxref{Frame Font}).
 
 @defun window-edges &optional window body absolute pixelwise
@@ -3903,7 +3903,7 @@ visible in some window:
 @end group
 @end example
 
-On a graphical terminal this form warps the mouse cursor to the
+On a graphical terminal this form ``warps'' the mouse cursor to the
 upper left corner of the glyph at the selected window's point.  A
 position calculated this way can be also used to show a tooltip window
 there.