From 95ad1ca967c0540ed5ed70fc2514c5d7b00f5f35 Mon Sep 17 00:00:00 2001 From: 0xflotus <0xflotus@gmail.com> Date: Mon, 8 Apr 2019 21:41:14 +0200 Subject: [PATCH] fixed some small errors (#117) --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 785ce0416..5be6d2169 100644 --- a/README.md +++ b/README.md @@ -277,7 +277,7 @@ definitions that may be helpful. ### Run-time Polymorphic This means that the API is driven by a virtual-table. This is simply a struct of function pointers. They are invoked via -a c extern style API, but ultimately those public functions simply invoke the cooresponding function in the v-table. +a c extern style API, but ultimately those public functions simply invoke the corresponding function in the v-table. These are reserved for types that: a.) Need to be configurable, changable at runtime @@ -349,7 +349,7 @@ This function is invoked when the event loop is finished processing and is ready int (*run) (struct aws_event_loop *); This function starts the running of the event loop and then immediately returns. This could kick off a thread, or setup some resources to run and -recieve events in a back channel API. For example, you could have an epoll loop that runs in a thread, or you could have an event loop pumped by a system +receive events in a back channel API. For example, you could have an epoll loop that runs in a thread, or you could have an event loop pumped by a system loop such as glib, or libevent etc... and then publish events to your event loop implementation. int (*stop) (struct aws_event_loop *, @@ -724,4 +724,4 @@ Reads from the socket. This call is non-blocking and will return `AWS_IO_SOCKET_ int aws_socket_write(struct aws_socket *socket, const struct aws_byte_buf *buffer, size_t *written); Writes to the socket. This call is non-blocking and will return `AWS_IO_SOCKET_WRITE_WOULD_BLOCK` if no data could be written. -`written` is the amount of data read from `buffer` and successfully written to `socket`. \ No newline at end of file +`written` is the amount of data read from `buffer` and successfully written to `socket`.