summaryrefslogtreecommitdiff
path: root/lispref/lists.texi
diff options
context:
space:
mode:
authorKarl Berry <karl@gnu.org>2006-07-16 18:25:23 +0000
committerKarl Berry <karl@gnu.org>2006-07-16 18:25:23 +0000
commitece35e15a7e73189b45b7c2d2fddcd6f46b0476f (patch)
treea785493e0cb209c32b27d5eac2a6fe1ec144ee03 /lispref/lists.texi
parent912c723552fdb9ff934d768e032b56c23911f2ab (diff)
fix bad page breaks
Diffstat (limited to 'lispref/lists.texi')
-rw-r--r--lispref/lists.texi8
1 files changed, 4 insertions, 4 deletions
diff --git a/lispref/lists.texi b/lispref/lists.texi
index 7de4a6c6ab..17d3ebc6c4 100644
--- a/lispref/lists.texi
+++ b/lispref/lists.texi
@@ -1412,8 +1412,8 @@ the value @code{cones}; the key @code{oak} is associated with
@end group
@end example
- The associated values in an alist may be any Lisp objects; so may the
-keys. For example, in the following alist, the symbol @code{a} is
+ Both the values and the keys in an alist may be any Lisp objects.
+For example, in the following alist, the symbol @code{a} is
associated with the number @code{1}, and the string @code{"b"} is
associated with the @emph{list} @code{(2 3)}, which is the @sc{cdr} of
the alist element:
@@ -1439,7 +1439,7 @@ below) to find the element containing a given value. When neither of
these considerations is important, the choice is a matter of taste, as
long as you are consistent about it for any given alist.
- Note that the same alist shown above could be regarded as having the
+ The same alist shown above could be regarded as having the
associated value in the @sc{cdr} of the element; the value associated
with @code{rose} would be the list @code{(red)}.
@@ -1557,7 +1557,7 @@ For example:
@result{} nil
@end smallexample
-Note that @code{rassq} cannot search for a value stored in the @sc{car}
+@code{rassq} cannot search for a value stored in the @sc{car}
of the @sc{cdr} of an element:
@smallexample