ami pushed a commit to branch master.

http://git.enlightenment.org/core/elementary.git/commit/?id=5db028a32de71ce167851e75b221499593d7cd89

commit 5db028a32de71ce167851e75b221499593d7cd89
Author: Amitesh Singh <amitesh...@samsung.com>
Date:   Sat Sep 19 09:13:09 2015 +0530

    fix typos in APIs doc
---
 src/lib/elm_app_server.eo  | 2 +-
 src/lib/elm_widget_item.eo | 4 ++--
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/src/lib/elm_app_server.eo b/src/lib/elm_app_server.eo
index 4cd82ea..fe82edc 100644
--- a/src/lib/elm_app_server.eo
+++ b/src/lib/elm_app_server.eo
@@ -53,7 +53,7 @@ class Elm_App_Server (Eo.Base)
          legacy: null;
          params {
             @in packageid: const(char)*; [[package of application]]
-            @in create_view_cb: Elm_App_Server_Create_View_Cb; [[callback to 
be called when user whants to open some application view]]
+            @in create_view_cb: Elm_App_Server_Create_View_Cb; [[callback to 
be called when user wants to open some application view]]
          }
       }
       close_all {
diff --git a/src/lib/elm_widget_item.eo b/src/lib/elm_widget_item.eo
index 1f61b96..48f4e44 100644
--- a/src/lib/elm_widget_item.eo
+++ b/src/lib/elm_widget_item.eo
@@ -385,7 +385,7 @@ class Elm.Widget_Item(Eo.Base, 
Elm_Interface_Atspi_Accessible,
                 [[This returns track object of the item.
 
                   Note: This gets a rectangle object that represents the 
object item's internal
-                  object. If you wanna check the geometry, visibility of the 
item, you
+                  object. If you want to check the geometry, visibility of the 
item, you
                   can call the evas apis such as evas_object_geometry_get(),
                   evas_object_visible_get() to the track object. Note that all 
of the
                   widget items may/may not have the internal object so this 
api may
@@ -424,7 +424,7 @@ class Elm.Widget_Item(Eo.Base, 
Elm_Interface_Atspi_Accessible,
 
                   Note: This gets the reference count for the track object. 
Whenever you call
                   the @.track, the reference count will be increased by
-                  one. Likely the referece count will be decreased again when 
you call
+                  one. Likely the reference count will be decreased again when 
you call
                   the @.untrack. Unless the reference count reaches to
                   zero, the track object won't be deleted. So please be sure 
to call
                   @.untrack() paired to the elm_object_item_track call

-- 


Reply via email to