Fix a couple of typos in various places.

examples/async-curl/src/http.c

@@ -112,7 +112,7 @@ state_result(struct http_request *req)
 	/* Get the state attached to the HTTP request. */
 	client = http_state_get(req);
 
-	/* Check if we were succesfull, if not log an error. */
+	/* Check if we were successful, if not log an error. */
 	if (!kore_curl_success(client)) {
 		kore_curl_logerror(client);
 		http_response(req, 500, NULL, 0);

examples/generic/src/example.c

@@ -45,7 +45,7 @@ char *b64tests[] = {
 	"any carnal pleasure.",
 	"any carnal pleasure",
 	"any carnal pleas",
-	"I am a nobody, nobody is perfect, therefor I am.",
+	"I am a nobody, nobody is perfect, therefore I am.",
 	NULL
 };
 

examples/jsonrpc/README.md

@@ -56,7 +56,7 @@ syslog. Messages are added with jsonrpc_log().
 By default messages of the log are added to the data member of the error
 responses if at levels EMERG, ERROR, WARNING and NOTICE.
 
-If you dont want log messages to be outputted zero the log_levels flag of the
+If you don't want log messages to be outputted zero the log_levels flag of the
 jsonrpc_request.
 
 

examples/nohttp/src/nohttp.c

@@ -50,7 +50,7 @@ connection_setup(struct connection *c)
 }
 
 /*
- * This function is called everytime a new event is triggered on the
+ * This function is called every time a new event is triggered on the
  * connection. In this demo we just use it as a stub for the normal
  * callback kore_connection_handle().
  *
@@ -69,7 +69,7 @@ connection_handle(struct connection *c)
 }
 
 /*
- * This function is called everytime we get up to 128 bytes of data.
+ * This function is called every time we get up to 128 bytes of data.
  * The connection can be found under nb->owner.
  * The data received can be found under nb->buf.
  * The length of the received data can be found under s_off.

examples/parameters/README.md

@@ -10,5 +10,5 @@ Test:
 	# curl -i -k https://127.0.0.1:8888/?id=123123
 ```
 
-The output will differ based on wether or not id is a valid
+The output will differ based on whether or not id is a valid
 u_int16_t number or not. (the string should always be present).

examples/python-pgsql/app.py

@@ -32,7 +32,7 @@ class KoreApp:
     # The query handler that fires of the query and returns a coroutine.
     #
     # Kore will resume this handler when the query returns a result or
-    # is succesfull.
+    # is successful.
     #
     # The kore.pgsql() method can throw exceptions, most notably a
     # GeneratorExit in case the client connection went away before

share/man/kodev.1

@@ -161,7 +161,7 @@ If set to \fByes\fR the build system will produce a single binary containing
 both your application code and the Kore code allowing you to distribute
 your application more easily.
 
-If set to \fBno\fR the build system will produce a standard dynamicly
+If set to \fBno\fR the build system will produce a standard dynamically
 linked library that will be loaded into Kore at runtime.
 .RE
 .RE

src/keymgr.c

@@ -1300,7 +1300,7 @@ keymgr_asn1_convert_utctime(const ASN1_TIME *na, time_t *out)
 
 	year = (na->data[0] - '0') * 10 + (na->data[1] - '0');
 
-	/* RFC 5280 says years >= 50 are intepreted as 19YY */
+	/* RFC 5280 says years >= 50 are interpreted as 19YY */
 	if (year >= 50)
 		year = 1900 + year;
 	else

src/worker.c

@@ -834,7 +834,7 @@ worker_unlock(void)
 {
 	accept_lock->current = 0;
 	if (!__sync_bool_compare_and_swap(&(accept_lock->lock), 1, 0))
-		kore_log(LOG_NOTICE, "worker_unlock(): wasnt locked");
+		kore_log(LOG_NOTICE, "worker_unlock(): wasn't locked");
 }
 
 static void