remove deprecated code related with

[framework/uifw/elementary.git] / doc / examples.dox

diff --git a/doc/examples.dox b/doc/examples.dox
index ea894ca..91a5d3e 100644 (file)
--- a/doc/examples.dox
+++ b/doc/examples.dox
@@ -1228,7 +1228,7 @@
  * If isn't required that users could select a day on calendar,
  * only interacting going through months, disabling days selection
  * could be a good idea to avoid confusion. For that:
- * @skipline elm_calendar_day_selection_enabled_set
+ * @skipline elm_calendar_day_selection_disabled_set
  *
  * Also, regarding days selection, you could be interested to set a
  * date to be highlighted on calendar from your code, maybe when
@@ -1329,7 +1329,7 @@
  * Periodicity is how frequently the mark will be displayed over the
  * calendar.  Can be a unique mark (that don't repeat), or it can repeat
  * daily, weekly, monthly or annually. It's enumerated by
- * @c Elm_Calendar_Mark_Repeat.
+ * @c Elm_Calendar_Mark_Repeat_Type.
  *
  * So let's add some marks to our calendar. We will add christmas holiday,
  * set Sundays as holidays, and check current day and day after that.
@@ -2096,7 +2096,7 @@
  * conversion
  * util functions, so we could get coordinates for this address. These
  * functions return an #Elm_Map_Name handle for us.
- * Function elm_map_utils_convert_name_into_coord() will do this job for us,
+ * Function elm_map_name_geo_request() will do this job for us,
  * but it's an assyncronous function, since it requires this
  * information from the server.
  *
@@ -2520,7 +2520,7 @@
  *
  * If you want to free this data, or handle that the way you need when the
  * item is deleted, set a callback function for that, with
- * elm_list_item_del_cb_set().
+ * elm_object_item_del_cb_set().
  *
  * As you can see we check if @c it is not @c NULL after appending it.
  * If an error happens, we won't try to set a function for it.