ecore: fix common misppellings

Mispellings detected by codespell.

git-svn-id: svn+ssh://svn.enlightenment.org/var/svn/e/trunk/ecore@61407 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33

diff --git a/doc/examples.dox b/doc/examples.dox
index 0d8b924..aa0034a 100644 (file)
--- a/doc/examples.dox
+++ b/doc/examples.dox
@@ -1043,7 +1043,7 @@
  * which will wooble 15 times and will decay by a factor of 1.2:
  * @until pos_map
  *
- * Now that we have the frame we can adjust the rectangle to its apropriate
+ * Now that we have the frame we can adjust the rectangle to its appropriate
  * state:
  * @until }
  *
@@ -1062,7 +1062,7 @@
  *
  * And for our last animation callback something simpler, we just move our
  * rectangle right by one pixel until it reaches the end of the screen and then
- * start at the beggining again:
+ * start at the beginning again:
  * @until }
  *
  * Our next two functions respectively freezes and thaw our third animation, so
@@ -1089,7 +1089,7 @@
  * Ecore Threads come in two flavors, short jobs and feedback jobs. Short jobs
  * just run the given function and are more commonly used for small tasks
  * where the main loop does not need to know how the work is going in between.
- * The short job in our example is so short we had to artifically enlarge it
+ * The short job in our example is so short we had to artificially enlarge it
  * with @c sleep(). Other than that, it also uses threads local data to keep
  * the data we are working with persistent across different jobs ran by the
  * same system thread. This data will be freed when the no more jobs are
@@ -1100,7 +1100,7 @@
  * part of the function checks in each iteration if it was cancelled by the
  * main loop, and if it was, it stops processing and clears the data from the
  * storage (we assume @c cancel means no one else will need this, but this is
- * really application dependant).
+ * really application dependent).
  * @dontinclude ecore_thread_example.c
  * @skip static void
  * @until sleep(1)

diff --git a/src/examples/ecore_fd_handler_example.c b/src/examples/ecore_fd_handler_example.c
index 8f37e3a..d80b290 100644 (file)
--- a/src/examples/ecore_fd_handler_example.c
+++ b/src/examples/ecore_fd_handler_example.c
@@ -22,7 +22,7 @@ _fd_handler_cb(void *data, Ecore_Fd_Handler *handler)
 
    if (ecore_main_fd_handler_active_get(handler, ECORE_FD_ERROR))
      {
-       printf("An error has occured. Stop watching this fd and quit.\n");
+       printf("An error has occurred. Stop watching this fd and quit.\n");
        ecore_main_loop_quit();
        ctxt->handler = NULL;
        return ECORE_CALLBACK_CANCEL;

diff --git a/src/lib/ecore/Ecore.h b/src/lib/ecore/Ecore.h
index c83bfd4..40a6346 100644 (file)
--- a/src/lib/ecore/Ecore.h
+++ b/src/lib/ecore/Ecore.h
@@ -1164,7 +1164,7 @@ extern "C" {
    * For example, if you have a program doing requisitions to a database,
    * these requisitions can be done in threads so that waiting for the
    * database to respond doesn't block the UI. Each of these threads will
-   * run a function, and each function will be dependant on a connection to
+   * run a function, and each function will be dependent on a connection to
    * the database, which may not be able to handle more than one request at
    * a time so for each running function you will need one connection handle.
    * The options then are: