X-Git-Url: http://git.chise.org/gitweb/?a=blobdiff_plain;f=man%2Flispref%2Fdragndrop.texi;h=8c2085cfd421596d0b2d15118a3d593e2ecd9b5e;hb=8c75f9dbdbda98aa07443a63dfa5a68873783994;hp=1757b61db5514eabc2518e535395842dde2e9d4b;hpb=6883ee56ec887c2c48abe5b06b5e66aa74031910;p=chise%2Fxemacs-chise.git.1

diff --git a/man/lispref/dragndrop.texi b/man/lispref/dragndrop.texi
index 1757b61..8c2085c 100644
--- a/man/lispref/dragndrop.texi
+++ b/man/lispref/dragndrop.texi
@@ -1,7 +1,7 @@
 @c -*-texinfo-*-
 @c This is part of the XEmacs Lisp Reference Manual.
 @c Copyright (C) 1998 Oliver Graf <ograf@fga.de>
-@c Original reference is (c) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc. 
+@c Original reference is (c) 1990, 1991, 1992, 1993, 1994 Free Software Foundation, Inc.
 @c See the file lispref.texi for copying conditions.
 @setfilename ../../info/dragndrop.texi
 @node Drag and Drop, Modes, Scrollbars, Top
@@ -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.
@@ -57,13 +57,13 @@ OffiX is supported if 'offix is member of the variable dragdrop-protocols, or
 the feature 'offix is defined.
 
 Unfortunately it uses it's own data types. Examples are: File, Files,
-Exe, Link, URL, MIME. The API tries to choose the right type for the data that 
+Exe, Link, URL, MIME. The API tries to choose the right type for the data that
 is dragged from XEmacs (well, not yet...).
 
-XEmacs supports both MIME and URL drags and drops using this API. No application 
+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
@@ -100,17 +100,17 @@ the XEmacs API, cause it also uses MIME types to encode dragged data.
 @cindex drop
 @cindex Drop API
 
-For each activated low-level protocol, a internal routine will catch
+For each activated low-level protocol, an internal routine will catch
 incoming drops and convert them to a dragdrop-drop type
 misc-user-event.
 
 This misc-user-event has its function argument set to
 @code{dragdrop-drop-dispatch} and the object contains the data of the drop
 (converted to URL/MIME specific data). This function will search the variable
-@code{experimental-dragdrop-drop-functions} for a function that can handle the 
+@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
@@ -118,7 +118,7 @@ extent-property with the same name. Extents are checked prior to the
 variable.
 
 The customization group @code{drag-n-drop} shows all variables of user
-interest. 
+interest.
 
 @node Drag Interface
 @section Drag Interface