From a72296839e771e76dceef604f93efe16b2428215 Mon Sep 17 00:00:00 2001 From: Otto Moerbeek Date: Mon, 12 Dec 2022 12:52:34 +0100 Subject: [PATCH] Apply suggestions from code review Co-authored-by: Peter van Dijk --- pdns/tcounters.hh | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/pdns/tcounters.hh b/pdns/tcounters.hh index c6956c68cb..90e3cf17ba 100644 --- a/pdns/tcounters.hh +++ b/pdns/tcounters.hh @@ -33,13 +33,13 @@ namespace pdns { // We keep three sets of related counters: // -// 1. The current counters (thread-local, updated individually by thread code very often) +// 1. The current counters (thread local, updated individually by thread code very often) // 2. The snapshot counters (thread local, updated by thread code in one single mutex protected copy) // 3. The history counters (global) to keep track of the counters of deleted threads -// We have two main clasess: one that holds the thread local counters +// We have two main classes: one that holds the thread local counters // (both current and snapshot ones) and one that aggregates the -// values for all threads adn keeps the history counters. +// values for all threads and keeps the history counters. // The thread local current counters are the ones updated by // performance critical code. Every once in a while, all values in the @@ -53,7 +53,7 @@ namespace pdns // in a while. This will fill the snapshot values for that thread if some // time has passed since the last snap update. -// To fet aggregate value call globals.sum(counter1) or +// To fetch aggregate values, call globals.sum(counter1) or // globals.avg(counter2), or any aggreggation function. If multiple // counters need to be collected in a consistent way: // auto data = globals.aggregatedSnap(); -- 2.47.2