aboutsummaryrefslogtreecommitdiff
path: root/src/validation.cpp
diff options
context:
space:
mode:
authorrandymcmillan <randy.lee.mcmillan@gmail.com>2019-11-04 04:22:53 -0500
committerrandymcmillan <randy.lee.mcmillan@gmail.com>2019-11-04 04:22:53 -0500
commitac831339cbfa65b1f7576c53b5d9a94841db9868 (patch)
tree4a8262bfa2dd49b03261f8bc6e0e85dc189cd8bb /src/validation.cpp
parent463eab5e1418a592036e7bf9bf46f66fe6462435 (diff)
doc: Fix some misspellings
Diffstat (limited to 'src/validation.cpp')
-rw-r--r--src/validation.cpp2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/validation.cpp b/src/validation.cpp
index ca6d2176b3..11072b6038 100644
--- a/src/validation.cpp
+++ b/src/validation.cpp
@@ -733,7 +733,7 @@ bool MemPoolAccept::PreChecks(ATMPArgs& args, Workspace& ws)
// To check these we first check if we meet the RBF criteria, above, and increment the descendant
// limits by the direct conflict and its descendants (as these are recalculated in
// CalculateMempoolAncestors by assuming the new transaction being added is a new descendant, with no
- // removals, of each parent's existing dependant set). The ancestor count limits are unmodified (as
+ // removals, of each parent's existing dependent set). The ancestor count limits are unmodified (as
// the ancestor limits should be the same for both our new transaction and any conflicts).
// We don't bother incrementing m_limit_descendants by the full removal count as that limit never comes
// into force here (as we're only adding a single transaction).