X-Git-Url: http://git.chise.org/gitweb/?p=chise%2Fxemacs-chise.git.1;a=blobdiff_plain;f=man%2Flispref%2Fdragndrop.texi;h=ceab662b5a07b14e5c82274433eac10f43332a56;hp=1757b61db5514eabc2518e535395842dde2e9d4b;hb=72a705551741d6f85a40eea486c222bac482d8dc;hpb=fb022c5b8ea6aca36b9661a6b2707afdd07e4c05

diff --git a/man/lispref/dragndrop.texi b/man/lispref/dragndrop.texi
index 1757b61..ceab662 100644
--- a/man/lispref/dragndrop.texi
+++ b/man/lispref/dragndrop.texi
@@ -12,7 +12,7 @@
 interface may change! The current implementation is considered experimental.
 
   Drag'n'drop is a way to transfer information between multiple applications.
-To do this serveral GUIs define their own protocols. Examples are OffiX, CDE,
+To do this several GUIs define their own protocols. Examples are OffiX, CDE,
 Motif, KDE, MSWindows, GNOME, and many more. To catch all these protocols,
 XEmacs provides a generic API.
 
@@ -32,7 +32,7 @@ powerful interfaces to support these types of data (tm and w3).
 @section Supported Protocols
 
 The current release of XEmacs only support a small set of Drag'n'drop
-protocols. Some of these only support limited options avaiable in the API.
+protocols. Some of these only support limited options available in the API.
 
 @menu
 * OffiX DND::           A generic X based protocol.
@@ -63,7 +63,7 @@ is dragged from XEmacs (well, not yet...).
 XEmacs supports both MIME and URL drags and drops using this API. No application 
 interaction is possible while dragging is in progress.
 
-For infomation about the OffiX project have a look at http://leb.net/~offix/
+For information about the OffiX project have a look at http://leb.net/~offix/
 
 @node CDE dt
 @subsection CDE dt
@@ -110,7 +110,7 @@ This misc-user-event has its function argument set to
 @code{experimental-dragdrop-drop-functions} for a function that can handle the 
 dropped data.
 
-To modify the drop behaviour, the user can modify the variable
+To modify the drop behavior, the user can modify the variable
 @code{experimental-dragdrop-drop-functions}. Each element of this list
 specifies a possible handler for dropped data. The first one that can handle
 the data will return @code{t} and exit. Another possibility is to set a