A few tiny doc/ copyedits.

diff --git a/doc/emacs/cmdargs.texi b/doc/emacs/cmdargs.texi
index 56137272be6a7a3232791418808ac6318c64e65d..3443f0b1627d35a1036b7b6c9817529ef79b4b42 100644 (file)
--- a/doc/emacs/cmdargs.texi
+++ b/doc/emacs/cmdargs.texi
@@ -989,7 +989,7 @@ tool bar when it processes the specified geometry.
 
   When using one of @samp{--fullscreen}, @samp{--maximized},
 @samp{--fullwidth} or @samp{--fullheight}, some window managers require
-to set the variable @code{frame-resize-pixelwise} to a non-@code{nil}
+you to set the variable @code{frame-resize-pixelwise} to a non-@code{nil}
 value to make a frame appear truly ``maximized'' or ``fullscreen''.
 
  Some window managers have options that can make them ignore both

diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index 92b5791051b4acb8fdea2c518a98fb95170e822f..03eba440a093f86748635524d4a2ff57d6761313 100644 (file)
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -971,7 +971,7 @@ variable do not take effect immediately, only when you specify the
 A list of symbols, specifying the @dfn{font backends} to use for
 drawing fonts in the frame, in order of priority.  On X, there are
 currently two available font backends: @code{x} (the X core font
-driver) and @code{xft} (the Xft font driver).  On Windows, there are
+driver) and @code{xft} (the Xft font driver).  On MS-Windows, there are
 currently two available font backends: @code{gdi} and
 @code{uniscribe} (@pxref{Windows Fonts,,, emacs, The GNU Emacs
 Manual}).  On other systems, there is only one available font backend,
@@ -1163,12 +1163,12 @@ size hints to the window manager.  This means that this variable should
 be set only in a user's initial file; applications should never bind it
 temporarily.
 
-The precise semantics of a value of @code{nil} for this option depends
-on the toolkit used: Dragging the frame border with the mouse is usually
-always done character-wise.  Calling @code{set-frame-size} (see below)
+The precise meaning of a value of @code{nil} for this option depends
+on the toolkit used.  Dragging the frame border with the mouse is usually
+done character-wise.  Calling @code{set-frame-size} (see below)
 with arguments that do not specify the frame size as an integer multiple
-of its character size may be, however, either ignored or cause a
-rounding (GTK+) or get accepted (Lucid, Motif, Windows).
+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''.