summaryrefslogtreecommitdiff
path: root/lispref/control.texi
diff options
context:
space:
mode:
authorKarl Heuer <kwzh@gnu.org>1999-07-27 21:01:02 +0000
committerKarl Heuer <kwzh@gnu.org>1999-07-27 21:01:02 +0000
commit3f63de1e217146f1f972df87ccb7d54e14d9e840 (patch)
tree8035c70b3637b2593bfa721000aeee07cc66659c /lispref/control.texi
parente7029763cae839439b8dc7d9fb90eb4a03de6a9c (diff)
downloademacs-3f63de1e217146f1f972df87ccb7d54e14d9e840.tar.gz
*** empty log message ***
Diffstat (limited to 'lispref/control.texi')
-rw-r--r--lispref/control.texi10
1 files changed, 5 insertions, 5 deletions
diff --git a/lispref/control.texi b/lispref/control.texi
index 17311fccf4b..2925201285b 100644
--- a/lispref/control.texi
+++ b/lispref/control.texi
@@ -9,7 +9,7 @@
@cindex control structures
A Lisp program consists of expressions or @dfn{forms} (@pxref{Forms}).
-We control the order of execution of the forms by enclosing them in
+We control the order of execution of these forms by enclosing them in
@dfn{control structures}. Control structures are special forms which
control when, whether, or how many times to execute the forms they
contain.
@@ -59,7 +59,7 @@ control construct of Lisp.
@end example
@noindent
-and it says to execute the forms @var{a}, @var{b}, @var{c} and so on, in
+and it says to execute the forms @var{a}, @var{b}, @var{c}, and so on, in
that order. These forms are called the body of the @code{progn} form.
The value of the last form in the body becomes the value of the entire
@code{progn}.
@@ -556,8 +556,8 @@ The return point is distinguished from other such return points by
@var{tag} is evaluated normally before the return point is established.
With the return point in effect, @code{catch} evaluates the forms of the
-@var{body} in textual order. If the forms execute normally, without
-error or nonlocal exit, the value of the last body form is returned from
+@var{body} in textual order. If the forms execute normally (without
+error or nonlocal exit) the value of the last body form is returned from
the @code{catch}.
If a @code{throw} is done within @var{body} specifying the same value
@@ -702,7 +702,7 @@ instead. @xref{Catch and Throw}.
Most errors are signaled ``automatically'' within Lisp primitives
which you call for other purposes, such as if you try to take the
@sc{car} of an integer or move forward a character at the end of the
-buffer; you can also signal errors explicitly with the functions
+buffer. You can also signal errors explicitly with the functions
@code{error} and @code{signal}.
Quitting, which happens when the user types @kbd{C-g}, is not