From 02bf7911f3afe6e5960349e5e61329afb3a995a9 Mon Sep 17 00:00:00 2001
From: un1versal
Date: Thu, 8 Oct 2015 13:10:17 +0100
Subject: [ci skip] no strings - cpp files - typo corrections

---
 src/kvilib/ext/KviCryptEngine.cpp | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'src/kvilib/ext/KviCryptEngine.cpp')

diff --git a/src/kvilib/ext/KviCryptEngine.cpp b/src/kvilib/ext/KviCryptEngine.cpp
index b52b6565c..6ec745cbd 100644
--- a/src/kvilib/ext/KviCryptEngine.cpp
+++ b/src/kvilib/ext/KviCryptEngine.cpp
@@ -129,7 +129,7 @@
 		Well, there is no protocol actually, only the existing implementations, that
 		can be accessed by anyone that want to reproduce them. There are only some
 		points relating to the crypting engines that need to be cleared:[br]
-		The crypted text must be suitable to be sent thru an IRC connection;
+		The crypted text must be suitable to be sent through an IRC connection;
 		this means that some characters can not appear in the crypted text (e.g. CR,LF,NULL....).
 		KVIrc solves it in a simple way: the crypted binary data is encoded,
 		either as hexadecimal numeric string or in base64.[br]
-- 
cgit v1.3.1-10-gc9f91