# HG changeset patch
# User Richard M. Stallman <rms@gnu.org>
# Date 1167936598 0
# Node ID 7d9ed49161f8622c48cfe1c417c3f7c33535c79f
# Parent  291b93cd991dc7ed1bdfb8b6d8bc4c823d350b32
(Windows Keyboard): Clarify previous change.

diff -r 291b93cd991d -r 7d9ed49161f8 man/msdog.texi
--- a/man/msdog.texi	Thu Jan 04 18:43:03 2007 +0000
+++ b/man/msdog.texi	Thu Jan 04 18:49:58 2007 +0000
@@ -336,12 +336,12 @@
 @cindex MS-Windows keyboard shortcuts
   Many key combinations (known as ``keyboard shortcuts'') that have
 conventional uses in MS-Windows programs conflict with traditional
-Emacs commands.  This conflict arose because the designers of Windows
-did not concern themselves with how Emacs used these characters.
-Examples include @kbd{C-c}, @kbd{C-x}, @kbd{C-z}, @kbd{C-a}, and
-@kbd{W-@key{SPC}}.  You can redefine some of them with meanings more
-like the MS-Windows meanings by enabling CUA Mode (@pxref{CUA
-Bindings}).
+Emacs commands.  This conflict arose because the designers of the CUA
+interface implemented by MS-Windows did not try to avoid conflict with
+Emacs.  Examples of conflicts include @kbd{C-c}, @kbd{C-x}, @kbd{C-z},
+@kbd{C-a}, and @kbd{W-@key{SPC}}.  You can redefine some of them with
+meanings more like the MS-Windows meanings by enabling CUA Mode
+(@pxref{CUA Bindings}).
 
 @kindex F10 @r{(MS-Windows)}
 @cindex menu bar access using keyboard @r{(MS-Windows)}