From: raster Date: Wed, 21 Mar 2012 11:54:28 +0000 (+0000) Subject: From: Jérôme Pinot X-Git-Tag: submit/trunk/20120815.174732~455 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=719dac94492c6384c79fc12d9304c6c040595dcb;p=profile%2Fivi%2Fevas.git From: Jérôme Pinot Subject: [E-devel] [patch] evas doc typos 3 typos in evas doc. git-svn-id: http://svn.enlightenment.org/svn/e/trunk/evas@69539 7cbeb6ba-43b4-40fd-8cce-4c39aea84d33 --- diff --git a/src/lib/Evas.h b/src/lib/Evas.h index 663a469..42eff3c 100644 --- a/src/lib/Evas.h +++ b/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. *