[ci skip] no strings - cpp files - typo corrections

2 files changed, 4 insertions, 4 deletions

diff --git a/src/kvilib/ext/KviAnimatedPixmapCache.cpp b/src/kvilib/ext/KviAnimatedPixmapCache.cpp
index 285945bab..dc436535e 100644
--- a/src/kvilib/ext/KviAnimatedPixmapCache.cpp
+++ b/src/kvilib/ext/KviAnimatedPixmapCache.cpp
@@ -183,10 +183,10 @@ void KviAnimatedPixmapCache::timeoutEvent()
 {
 	/*
 	* We are adding 15msecs to the current time. This MAY lead to the situation,
-	* when the current frame will be painted a bit earlier, then i should.
-	* But we are just playing animated gifs, not a HDTV video. So it should be ok.
+	* when the current frame will be painted a bit earlier, then I should.
+	* But we are just playing animated gifs, not a HDTV video. So it should be OK.
 	*
-	* But it makes good speedup if there will be event, sceduled in such order:
+	* But it makes good speedup if there will be event, scheduled in such order:
 	* 1 event  at time X
 	* 3 events at time X+2msec
 	* 2 events at time X+6msec
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]