Fix some typos (found by codespell)

Signed-off-by: Stefan Weil <sw@weilnetz.de>

4 files changed, 5 insertions, 5 deletions

diff --git a/libvncserver/tightvnc-filetransfer/filetransfermsg.c b/libvncserver/tightvnc-filetransfer/filetransfermsg.c
index 88fbe9a..153f123 100644
--- a/libvncserver/tightvnc-filetransfer/filetransfermsg.c
+++ b/libvncserver/tightvnc-filetransfer/filetransfermsg.c
@@ -108,8 +108,8 @@ GetFileListResponseMsg(char* path, char flags)
 
 	
 	 /* fileListInfo can have null data if the folder is Empty 
-    	or if some error condition has occured.
-    	The return value is 'failure' only if some error condition has occured.
+	or if some error condition has occurred.
+	The return value is 'failure' only if some error condition has occurred.
 	 */
 	status = CreateFileListInfo(&fileListInfo, path, !(flags  & 0x10));
 
diff --git a/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c b/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
index 431912e..b235fa0 100644
--- a/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
+++ b/libvncserver/tightvnc-filetransfer/handlefiletransferrequest.c
@@ -703,7 +703,7 @@ HandleFileUploadLengthError(rfbClientPtr cl, short fNameSize)
 	    return;
 	}
 
-	rfbLog("File [%s]: Method [%s]: File Upload Length Error occured"
+	rfbLog("File [%s]: Method [%s]: File Upload Length Error occurred"
 			"file path requested is <%s>\n", __FILE__, __FUNCTION__, path);
 
     if(path != NULL) {
diff --git a/libvncserver/tightvnc-filetransfer/rfbtightproto.h b/libvncserver/tightvnc-filetransfer/rfbtightproto.h
index ef683ae..d0fe642 100644
--- a/libvncserver/tightvnc-filetransfer/rfbtightproto.h
+++ b/libvncserver/tightvnc-filetransfer/rfbtightproto.h
@@ -208,7 +208,7 @@ void rfbHandleSecTypeTight(rfbClientPtr cl);
  * In the protocol version 3.7t, the server informs the client what message
  * types it supports in addition to ones defined in the protocol version 3.7.
  * Also, the server sends the list of all supported encodings (note that it's
- * not necessary to advertise the "raw" encoding sinse it MUST be supported in
+ * not necessary to advertise the "raw" encoding since it MUST be supported in
  * RFB 3.x protocols).
  *
  * This data immediately follows the server initialisation message.
diff --git a/libvncserver/tightvnc-filetransfer/rfbtightserver.c b/libvncserver/tightvnc-filetransfer/rfbtightserver.c
index d43d3f3..67d4cb5 100644
--- a/libvncserver/tightvnc-filetransfer/rfbtightserver.c
+++ b/libvncserver/tightvnc-filetransfer/rfbtightserver.c
@@ -500,7 +500,7 @@ rfbHandleSecTypeTight(rfbClientPtr cl) {
 
     if(rtcp == NULL) {
         /* Error condition close socket */
-        rfbLog("Memory error has occured while handling "
+        rfbLog("Memory error has occurred while handling "
 		"Tight security type... closing connection.\n");
 	 rfbCloseClient(cl);
 	 return;