scratch/sqlite 8bc9c80: Copy edit the multisession docs a bit

[Lars Ingebrigtsen]

branch: scratch/sqlite
commit 8bc9c80292e988a216c4fd98762a217af9292a40
Author: Lars Ingebrigtsen <larsi@gnus.org>
Commit: Lars Ingebrigtsen <larsi@gnus.org>

    Copy edit the multisession docs a bit
---
 doc/lispref/variables.texi | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/doc/lispref/variables.texi b/doc/lispref/variables.texi
index 586ad98..c07d795 100644
--- a/doc/lispref/variables.texi
+++ b/doc/lispref/variables.texi
@@ -2783,12 +2783,12 @@ to be used, here's a small example:
 
 This defines the variable @code{foo-var} and binds it to a special
 multisession object which is initialized with the value @samp{0} (if
-it doesn't already exist from a previous session).  The
-@code{my-adder} function queries the user for a number, adds this to
+the variable doesn't already exist from a previous session).  The
+@code{my-adder} command queries the user for a number, adds this to
 the old (possibly saved value), and then saves the new value.
 
 This facility isn't meant to be used for huge data structures, but
-should be reasonably performant for most values.
+should be performant for most values.
 
 @defmac define-multisession-variable name initial-value &optional doc &rest 
args
 This macro defines @var{name} as a multisession variable, with using
@@ -2830,6 +2830,9 @@ way to update a variable is to say, for instance:
 (setf (multisession-value foo-bar) 'zot)
 @end lisp
 
+Only Emacs Lisp values that have a readable print syntax can be saved
+this way.
+
 If the multisession variable is synchronized, setting it may update
 the value first.  For instance: