From 058b7bd3c5aa52365d3cfe0e69aa6212da6f30c2 Mon Sep 17 00:00:00 2001
From: zivillian <devel@zivillian.de>
Date: Tue, 5 Oct 2021 22:16:31 +0200
Subject: [PATCH] fix typo

---
 doc/CreateMeter.md         | 4 ++--
 src/meters.cc              | 2 +-
 tests/test_key_warnings.sh | 4 ++--
 tests/test_unknown.sh      | 4 ++--
 4 files changed, 7 insertions(+), 7 deletions(-)

diff --git a/doc/CreateMeter.md b/doc/CreateMeter.md
index cdc5086..84484c4 100644
--- a/doc/CreateMeter.md
+++ b/doc/CreateMeter.md
@@ -29,7 +29,7 @@ If you now start wmbusmeters with `wmbusmeters --debug --verbose useconfig=/` an
 
 ```
 [2021-07-05_21:07:30] (meter) ABOGGLKZ: meter detection did not match the selected driver eurisii! correct driver is: unknown!
-(meter) Not printing this warning agin for id: 60900126 mfct: (AAA) Aventies, Germany (0x421) type: Heat Cost Allocator (0x08) ver: 0x55
+(meter) Not printing this warning again for id: 60900126 mfct: (AAA) Aventies, Germany (0x421) type: Heat Cost Allocator (0x08) ver: 0x55
 [2021-07-05_21:07:30] (meter) please consider opening an issue at https://github.com/weetmuts/wmbusmeters/
 [2021-07-05_21:07:30] (meter) to add support for this unknown mfct,media,version combination
 (meter) ABOGGLKZ: yes for me
@@ -140,7 +140,7 @@ telegram=|76442104260190605508722601906021045508060060052F2F|0B6E660100426EA6008
 Now keep especially the following lines in mind for integation into the meter definitions:
 ```
 [2021-07-05_21:07:30] (meter) ABOGGLKZ: meter detection did not match the selected driver eurisii! correct driver is: unknown!
-(meter) Not printing this warning agin for id: 60900126 mfct: (AAA) Aventies, Germany (0x421) type: Heat Cost Allocator (0x08) ver: 0x55
+(meter) Not printing this warning again for id: 60900126 mfct: (AAA) Aventies, Germany (0x421) type: Heat Cost Allocator (0x08) ver: 0x55
 ```
 
 ## Creating your class
diff --git a/src/meters.cc b/src/meters.cc
index 01a1030..1accd35 100644
--- a/src/meters.cc
+++ b/src/meters.cc
@@ -513,7 +513,7 @@ bool MeterCommonImplementation::isTelegramForMeter(Telegram *t, Meter *meter, Me
         {
             string possible_drivers = t->autoDetectPossibleDrivers();
             warning("(meter) %s: meter detection did not match the selected driver %s! correct driver is: %s\n"
-                    "(meter) Not printing this warning agin for id: %02x%02x%02x%02x mfct: (%s) %s (0x%02x) type: %s (0x%02x) ver: 0x%02x\n",
+                    "(meter) Not printing this warning again for id: %02x%02x%02x%02x mfct: (%s) %s (0x%02x) type: %s (0x%02x) ver: 0x%02x\n",
                     name.c_str(),
                     toString(driver).c_str(),
                     possible_drivers.c_str(),
diff --git a/tests/test_key_warnings.sh b/tests/test_key_warnings.sh
index 86787ab..a9e5b6d 100755
--- a/tests/test_key_warnings.sh
+++ b/tests/test_key_warnings.sh
@@ -12,7 +12,7 @@ $PROG --format=json simulations/simulation_bad_keys.txt room fhkvdataiii 0306571
 
 cat > $TEST/expected_err.txt <<EOF
 (meter) room: meter detection did not match the selected driver fhkvdataiii! correct driver is: fhkvdataiv
-(meter) Not printing this warning agin for id: 03065716 mfct: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x08) ver: 0x94
+(meter) Not printing this warning again for id: 03065716 mfct: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x08) ver: 0x94
 (wmbus) decrypted content failed check, did you use the correct decryption key? Permanently ignoring telegrams from id: 03065716 mfct: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x08) ver: 0x94
 EOF
 
@@ -27,7 +27,7 @@ $PROG --format=json simulations/simulation_bad_keys.txt room fhkvdataiv 03065716
 
 cat > $TEST/expected_err.txt <<EOF
 (meter) room: meter detection did not match the selected driver fhkvdataiv! correct driver is: fhkvdataiii
-(meter) Not printing this warning agin for id: 03065716 mfct: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x94
+(meter) Not printing this warning again for id: 03065716 mfct: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x80) ver: 0x94
 (wmbus) decrypted content failed check, did you use the correct decryption key? Permanently ignoring telegrams from id: 03065716 mfct: (TCH) Techem Service (0x5068) type: Heat Cost Allocator (0x08) ver: 0x94
 EOF
 
diff --git a/tests/test_unknown.sh b/tests/test_unknown.sh
index b6a9b97..a9bcd3c 100755
--- a/tests/test_unknown.sh
+++ b/tests/test_unknown.sh
@@ -14,12 +14,12 @@ Forren lansensm 00010206 NOKEY
 
 cat > $TEST/test_expected.txt <<EOF
 (meter) Dorren: meter detection did not match the selected driver lansendw! correct driver is: unknown!
-(meter) Not printing this warning agin for id: 00010205 mfct: (LAS) Lansen Systems, Sweden (0x3033) type: Unknown (0xff) ver: 0x07
+(meter) Not printing this warning again for id: 00010205 mfct: (LAS) Lansen Systems, Sweden (0x3033) type: Unknown (0xff) ver: 0x07
 (meter) please consider opening an issue at https://github.com/weetmuts/wmbusmeters/
 (meter) to add support for this unknown mfct,media,version combination
 {"media":"Unknown","meter":"lansendw","name":"Dorren","id":"00010205","status":"OPEN","timestamp":"1111-11-11T11:11:11Z"}
 (meter) Forren: meter detection did not match the selected driver lansensm! correct driver is: lansendw
-(meter) Not printing this warning agin for id: 00010206 mfct: (LAS) Lansen Systems, Sweden (0x3033) type: Reserved for sensors (0x1d) ver: 0x07
+(meter) Not printing this warning again for id: 00010206 mfct: (LAS) Lansen Systems, Sweden (0x3033) type: Reserved for sensors (0x1d) ver: 0x07
 {"media":"reserved","meter":"lansensm","name":"Forren","id":"00010206","status":"OK","timestamp":"1111-11-11T11:11:11Z"}
 {"media":"Unknown","meter":"lansendw","name":"Dorren","id":"00010205","status":"OPEN","timestamp":"1111-11-11T11:11:11Z"}
 {"media":"reserved","meter":"lansensm","name":"Forren","id":"00010206","status":"OK","timestamp":"1111-11-11T11:11:11Z"}