* lispref/commands.texi (Defining Commands): Copyedit re `interactive-only'.

2 files changed, 8 insertions, 5 deletions

diff --git a/doc/lispref/ChangeLog b/doc/lispref/ChangeLog
index c2d6c8d7012..331784ecae0 100644
--- a/doc/lispref/ChangeLog
+++ b/doc/lispref/ChangeLog
@@ -1,3 +1,7 @@
+2014-03-21  Glenn Morris  <rgm@gnu.org>
+
+        * commands.texi (Defining Commands): Copyedit re `interactive-only'.
+
 2014-03-20  Paul Eggert  <eggert@cs.ucla.edu>
 
         * internals.texi (C Integer Types): Prefer 'false' and 'true'
diff --git a/doc/lispref/commands.texi b/doc/lispref/commands.texi
index 5c28522158a..198926a9a6a 100644
--- a/doc/lispref/commands.texi
+++ b/doc/lispref/commands.texi
@@ -123,11 +123,10 @@ value for this property takes precedence over any @code{interactive}
 form in the function body itself.  This feature is seldom used.
 
 @cindex @code{interactive-only} property
-  Sometimes, a named command is only intended to be called
-interactively, never directly from Lisp.  In that case, give it a
-non-@code{nil} @code{interactive-only} property.  In that case, the
-byte compiler will print a warning message if the command is called
-from Lisp.
+  Sometimes, a function is only intended to be called interactively,
+never directly from Lisp.  In that case, give the function a
+non-@code{nil} @code{interactive-only} property.  This causes the
+byte compiler to warn if the command is called from Lisp.
 
 @menu
 * Using Interactive::     General rules for @code{interactive}.