Documentation copy-edits

* doc/emacs/input.texi (Touchscreens):

* doc/lispref/frames.texi (Other Selections): Insubstantial
copy-edits and improvements to word choice.

diff --git a/doc/emacs/input.texi b/doc/emacs/input.texi
index 5b559652896f8985bda9b73845407b3ef56bb401..0dd7fca41ccc698f82634bff3bd46243a3327120 100644 (file)
--- a/doc/emacs/input.texi
+++ b/doc/emacs/input.texi
@@ -25,11 +25,12 @@ which is detailed here.
 
   Touchscreen input is the manipulation of a frame's contents by the
 placement and motion of tools (instanced by fingers and such pointing
-devices as styluses) on a monitor or computer terminal where a frame
-is displayed.
+devices as styluses) on a monitor or computer terminal where it is
+displayed.
 
-  Under the X Window System or Android, Emacs detects and maps the
-following sequences of movements (``gestures'') to common actions:
+  Under the X Window System or Android, Emacs detects and translates
+the following sequences of movements (@dfn{gestures}) to common
+actions:
 
 @itemize @bullet
 @item
@@ -58,7 +59,7 @@ this gesture.
 tool on the display and leaving it there awhile before moving it to
 another position, will move point to the tool's initial position, and
 commence selecting text under the tool as it continues its motion, as
-if @code{mouse-1} were to be held down and a mouse moved anologously.
+if @code{mouse-1} were to be held down and a mouse moved analogously.
 @xref{Mouse Commands}.
 
 @vindex touch-screen-word-select

diff --git a/doc/lispref/frames.texi b/doc/lispref/frames.texi
index fb19317cedf9439acebc09bf058dd9dbec2711f8..1a7af04b103bb648419cd0a4ef7d4e28274cae4f 100644 (file)
--- a/doc/lispref/frames.texi
+++ b/doc/lispref/frames.texi
@@ -4670,10 +4670,17 @@ startup (@emph{not} a timestamp), and that for the other is a vector
 of available selection data types, as elsewhere.
 
 @cindex Android selections
-  Under Android, @code{gui-get-selection} is capable of returning
-UTF-8 string data of the type @code{STRING}, or image and application
-data associated with a MIME type.  @code{gui-set-selection} will only
-set string data, as on MS-Windows.
+  Much like MS-Windows, Android provides a clipboard but no primary or
+secondary selection; @code{gui-set-selection} simulates the primary
+selection by saving the value supplied into a variable subsequent
+calls to @code{gui-get-selection} return.
+
+  From the clipboard, @code{gui-get-selection} is capable of returning
+UTF-8 string data of the type @code{STRING}, the @code{TAREGTS} data
+type, or image and application data of any MIME type.
+@code{gui-set-selection} sets only string data, much as under
+MS-Windows, although this data is not affected by the value of
+@code{selection-coding-system}.
 
 @node Yanking Media
 @section Yanking Media