diff --git a/twander.1 b/twander.1
index 0eb79bf..0be181a 100644
--- a/twander.1
+++ b/twander.1
@@ -3057,9 +3057,19 @@
 Notice that Execution Variables are delimited by backticks, not single-quotes.
 
 .IP \(bu 4
-If you have something like \fC[\`program\`]\fP in a Command Definition,
-it will be replaced with any text that "program" produces as it runs.
-That text will have any trailing newline stripped.
+If you have something like \fC[\`program\`]\fP in a Command
+Definition, it will be replaced with any text that "program" produces
+as it runs.  That text will have any trailing newline stripped.
+Notice that this is different that most \fCtwander\fP variables that
+are evaluated once when the configuration file is first read in.
+
+This is true wherever the execution variable appears - either as the
+right-hand-side of a variable statement or explicitly inline within a
+command definition.  You can confirm this by looking at the
+\fCUser-Defined Variables\fP and \fCCommand Definitions\fP help menus.
+Anything referencing an execution variable will show the command to be
+executed when the variable is actually referenced at command
+invocation time.
 
 .IP \(bu 4
 Suppose you want to populate an Execution Variable with a program that
@@ -4819,4 +4829,4 @@
 .ft \" revert
 
 .SH DOCUMENT REVISION INFORMATION
-$Id: twander.1,v 1.131 2006/12/14 08:24:28 tundra Exp $
\ No newline at end of file
+$Id: twander.1,v 1.132 2006/12/14 08:47:30 tundra Exp $
\ No newline at end of file