Fixed typos

conf/kore.conf.example

@@ -95,7 +95,7 @@ validator	v_session	function	v_session_validate
 #tls_dhparam	dh2048.pem
 
 # Specify the amount of seconds a SPDY connection is kept open.
-# You can keep it open indefinately by setting this to 0.
+# You can keep it open indefinitely by setting this to 0.
 #spdy_idle_time		120
 
 # Authentication configuration
@@ -118,7 +118,7 @@ authentication auth_example {
 	# Allow values:
 	#	- cookie (checks for the cookie presence + pass to validator)
 	#	- header (checks for header presence + pass to validator)
-	#	- requuest (passes the http_request to the validator)
+	#	- request (passes the http_request to the validator)
 	#
 	# Use cases for request could for example be IP based ACLs or
 	# any other criteria that can be extracted from a http_request.

examples/parameters/src/parameters.c

@@ -42,7 +42,7 @@ page(struct http_request *req)
 	 * get any parameters returned from Kore.
 	 *
 	 * http_populate_arguments() returns the number of arguments
-	 * that were succesfully processed and are available.
+	 * that were successfully processed and are available.
 	 */
 	p = http_populate_arguments(req);
 

examples/pgsql/src/pgsql.c

@@ -183,7 +183,7 @@ request_db_read(struct http_request *req)
 	return (HTTP_STATE_CONTINUE);
 }
 
-/* An error occured. */
+/* An error occurred. */
 int
 request_error(struct http_request *req)
 {

examples/tasks/src/tasks.c

@@ -101,7 +101,7 @@ page_handler(struct http_request *req)
 	 * Our page handler is scheduled to be called when either the
 	 * task finishes or has written data onto the channel.
 	 *
-	 * In order to distuingish between the two we can inspect the
+	 * In order to distinguish between the two we can inspect the
 	 * state of the task.
 	 */
 	if (kore_task_state(&state->task) != KORE_TASK_STATE_FINISHED) {

examples/websocket/README.md

@@ -13,5 +13,5 @@ Test:
 	Hit the connect button to open a websocket session, open a second
 	tab and surf to the same address and hit the connection button there
 	as well. This should cause the number of messages sent/recv to keep
-	incremementing as each message is broadcast to the other connection.
+	incrementing as each message is broadcast to the other connection.
 ```