(Positions): Clarify converting marker to integer.

diff --git a/lispref/positions.texi b/lispref/positions.texi
index 822238a6342f85ed7ffb6c3fb7afe07b32017fbb..9a71cf29e3326b465fa1f9aebf9b671b94bbd215 100644 (file)
--- a/lispref/positions.texi
+++ b/lispref/positions.texi
@@ -15,14 +15,16 @@ speak of the character before or after a given position.  However, we
 often speak of the character ``at'' a position, meaning the character
 after that position.
 
-  Positions are usually represented as integers starting from 1, but can
-also be represented as @dfn{markers}---special objects that relocate
-automatically when text is inserted or deleted so they stay with the
-surrounding characters.  Functions that expect an argument to be a
-position (an integer), but accept a marker as a substitute, normally
-ignore the marker buffer.  Of course, markers used this way usually
-point to a position in the buffer that the function operates on, but
-that is entirely the programmer's responsibility.  @xref{Markers}.
+  Positions are usually represented as integers starting from 1, but
+can also be represented as @dfn{markers}---special objects that
+relocate automatically when text is inserted or deleted so they stay
+with the surrounding characters.  Functions that expect an argument to
+be a position (an integer), but accept a marker as a substitute,
+normally ignore which buffer the marker points into; they convert the
+marker to an integer, and use that integer, exactly as if you had
+passed the integer as the argument.  Markers used this way usually
+point to a position in the buffer that the function will operate on,
+but if not, they are converted to integers anyway.  @xref{Markers}.
 
   See also the ``field'' feature (@pxref{Fields}), which provides
 functions that are used by many cursor-motion commands.