[Emacs-diffs] /srv/bzr/emacs/trunk r107708: lispref/edebug.texi copyedits

[Glenn Morris]

------------------------------------------------------------
revno: 107708
committer: Glenn Morris <address@hidden>
branch nick: trunk
timestamp: Fri 2012-03-30 21:09:30 -0400
message:
  lispref/edebug.texi copyedits
  
  * doc/lispref/edebug.texi (Edebug Eval, Specification List, Edebug Options):
  Copyedits.
modified:
  doc/lispref/ChangeLog
  doc/lispref/edebug.texi

=== modified file 'doc/lispref/ChangeLog'
--- a/doc/lispref/ChangeLog     2012-03-30 16:31:24 +0000
+++ b/doc/lispref/ChangeLog     2012-03-31 01:09:30 +0000
@@ -1,3 +1,8 @@
+2012-03-31  Glenn Morris  <address@hidden>
+
+       * edebug.texi (Edebug Eval, Specification List, Edebug Options):
+       Copyedits.
+
 2012-03-30  Chong Yidong  <address@hidden>
 
        * display.texi (Image Formats): Add imagemagick type.

=== modified file 'doc/lispref/edebug.texi'
--- a/doc/lispref/edebug.texi   2012-03-30 16:12:37 +0000
+++ b/doc/lispref/edebug.texi   2012-03-31 01:09:30 +0000
@@ -629,7 +629,7 @@
 @node Edebug Eval
 @subsection Evaluation
 
-  While within Edebug, you can evaluate expressions ``as if'' Edebug
+  While within Edebug, you can evaluate expressions as if Edebug
 were not running.  Edebug tries to be invisible to the expression's
 evaluation and printing.  Evaluation of expressions that cause side
 effects will work as expected, except for changes to data that Edebug
@@ -656,6 +656,7 @@
 lexically bound symbols created by the following constructs in
 @file{cl.el}: @code{lexical-let}, @code{macrolet}, and
 @code{symbol-macrolet}.
address@hidden FIXME?  What about lexical-binding = t?
 
 @node Eval List
 @subsection Evaluation List Buffer
@@ -1170,7 +1171,7 @@
 @dfn{specification keywords}, are symbols beginning with @samp{&} (such
 as @code{&optional}).
 
-A specification list may contain sublists which match arguments that are
+A specification list may contain sublists, which match arguments that are
 themselves lists, or it may contain vectors used for grouping.  Sublists
 and groups thus subdivide the specification list into a hierarchy of
 levels.  Specification keywords apply only to the remainder of the
@@ -1221,7 +1222,7 @@
 All following elements in the specification list are optional; as soon
 as one does not match, Edebug stops matching at this level.
 
-To make just a few elements optional followed by non-optional elements,
+To make just a few elements optional, followed by non-optional elements,
 use @code{[&optional @address@hidden  To specify that several
 elements must all match or none, use @code{&optional
 address@hidden@dots{}]}.  See the @code{defun} example.
@@ -1286,8 +1287,8 @@
 just as for macros.  See the @code{defun} example.
 
 Otherwise, the symbol should be a predicate.  The predicate is called
-with the argument and the specification fails if the predicate returns
address@hidden, and the argument is not instrumented.
+with the argument, and if the predicate returns @code{nil}, the
+specification fails and the argument is not instrumented.
 
 Some suitable predicates include @code{symbolp}, @code{integerp},
 @code{stringp}, @code{vectorp}, and @code{atom}.
@@ -1482,8 +1483,8 @@
 @defopt edebug-setup-hook
 Functions to call before Edebug is used.  Each time it is set to a new
 value, Edebug will call those functions once and then
address@hidden is reset to @code{nil}.  You could use this to
-load up Edebug specifications associated with a package you are using
+reset @code{edebug-setup-hook} to @code{nil}.  You could use this to
+load up Edebug specifications associated with a package you are using,
 but only when you also use Edebug.
 @xref{Instrumenting}.
 @end defopt