aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2023-12-04 13:43:04 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2023-12-04 13:43:04 +0200
commitd4234c2c011d0fdcce6dc9006741373f048db942 (patch)
tree2e10eca72f1d9667ee44b2ea7ac740771537ff93
parent2ee43600a9090d1eb39a4bfd7fe70c795e16e7e9 (diff)
Clarify comment
-rw-r--r--libbuild2/algorithm.hxx8
1 files changed, 4 insertions, 4 deletions
diff --git a/libbuild2/algorithm.hxx b/libbuild2/algorithm.hxx
index 456862d..c8f1d81 100644
--- a/libbuild2/algorithm.hxx
+++ b/libbuild2/algorithm.hxx
@@ -255,10 +255,10 @@ namespace build2
// If the target is already applied (for this action) or executed, then no
// lock is acquired. Otherwise, unless matched is true, the target must not
- // be matched but not yet applied for this action (and if that's the case
- // and matched is true, then you get a locked target that you should
- // probably check for consistency, for exmaple, by comparing the matched
- // rule).
+ // be in the matched but not yet applied state for this action (and if
+ // that's the case and matched is true, then you get a locked target that
+ // you should probably check for consistency, for example, by comparing the
+ // matched rule).
//
// @@ MT fuzzy: what if it is already in the desired state, why assert?
// Currently we only use it with match_recipe/rule() and if it is matched