[gimp-web: 1/2] Variables available in podregister may also be auto-supplied by Gimp::Fu.

[Ed J <edj src gnome org>]

commit df710091a48d91bc2e208b11e4caac201aacf15b
Author: Ed J <edj src gnome org>
Date:   Sun May 4 04:23:36 2014 +0100

    Variables available in podregister may also be auto-supplied by Gimp::Fu.

 tutorials/Basic_Perl/index.htrw |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)
---
diff --git a/tutorials/Basic_Perl/index.htrw b/tutorials/Basic_Perl/index.htrw
index bcc7461..bd8e175 100644
--- a/tutorials/Basic_Perl/index.htrw
+++ b/tutorials/Basic_Perl/index.htrw
@@ -360,11 +360,11 @@ script_fu_basic1_logo("Hello", 72,
 <h3><a name="SEC5.2">5.2. podregister parameters</a></h3>
 
 You will have noticed above that the parameters to the function given
-to <tt>podregister</tt> used parameters named in the POD such as
-<tt>$drawable</tt>. This is because <tt>podregister</tt> automatically
-makes available to your function all the variables declared either in the
-POD documentation (the "PARAMETERS" section) or added depending on your
-"image types".
+to <tt>podregister</tt> used parameters either named in the POD, or
+supplied by <tt>Gimp::Fu</tt>, such as <tt>$drawable</tt>. This is because
+<tt>podregister</tt> automatically makes available to your function all
+the variables declared either in the POD documentation (the "PARAMETERS"
+section) or added depending on your "image types".
 
 <h3><a name="SEC5.3">5.3. A commented script</a></h3>