Use target recipe for auxiliary data storage during match-apply

In particular, we now have separate auxiliary data storage for inner
and outer operations.

1 files changed, 3 insertions, 2 deletions

diff --git a/libbuild2/in/rule.hxx b/libbuild2/in/rule.hxx
index 98ab3b4..bd0d15a 100644
--- a/libbuild2/in/rule.hxx
+++ b/libbuild2/in/rule.hxx
@@ -18,8 +18,9 @@ namespace build2
   {
     // Preprocess an .in file.
     //
-    // Note that a derived rule can use the target data pad to cache data
-    // (e.g., in match() or apply()) to be used in substitute/lookup() calls.
+    // Note that a derived rule can use the target auxiliary data storage to
+    // cache data (e.g., in match() or apply()) to be used in substitute() and
+    // lookup() calls.
     //
     // Note also that currently this rule ignores the dry-run mode (see
     // perform_update() for the rationale).