From 5900e0c9530260a82cf1d50276f0eb9459bd0f43 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?J=C3=A9r=C3=B4me=20Pinot?= Date: Wed, 21 Mar 2012 11:54:28 +0000 Subject: [PATCH] =?UTF-8?q?From:=20J=C3=A9r=C3=B4me=20Pinot=20=20Subject:=20[E-devel]=20[patch]=20evas=20doc=20typos?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 3 typos in evas doc. SVN revision: 69539 --- legacy/evas/src/lib/Evas.h | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/legacy/evas/src/lib/Evas.h b/legacy/evas/src/lib/Evas.h index 663a469f80..42eff3cd4c 100644 --- a/legacy/evas/src/lib/Evas.h +++ b/legacy/evas/src/lib/Evas.h @@ -2424,7 +2424,7 @@ EAPI Evas_Event_Flags evas_event_default_flags_get (const Evas *e) EINA_AR * of this kind during the freeze will get @b discarded. Every freeze * call must be matched by a thaw call in order to completely thaw out * a canvas (i.e. these calls may be nested). The most common use is - * when you don't want the user to interect with your user interface + * when you don't want the user to interact with your user interface * when you're populating a view or changing the layout. * * Example: @@ -9716,7 +9716,7 @@ EAPI int evas_smart_usage_get(const Evas_Smart *s); * used on the icon object. * * Besides that, generally smart objects implement a specific - * API, so that users interect with its own custom features. The + * API, so that users interact with its own custom features. The * API takes form of explicit exported functions one may call and * smart callbacks. * @@ -9730,7 +9730,7 @@ EAPI int evas_smart_usage_get(const Evas_Smart *s); * definition for the callback functions: #Evas_Smart_Cb. * * When defining an #Evas_Smart_Class, smart object implementors are - * strongly encorauged to properly set the Evas_Smart_Class::callbacks + * strongly encouraged to properly set the Evas_Smart_Class::callbacks * callbacks description array, so that the users of the smart object * can have introspection on its events API at run time. *