elm elm_widget.h elm_widget_layout.h: Fixed typo.

SVN revision: 71611

diff --git a/src/lib/elm_widget.h b/src/lib/elm_widget.h
index a7cccf9..7e4df80 100644 (file)
--- a/src/lib/elm_widget.h
+++ b/src/lib/elm_widget.h
@@ -239,7 +239,7 @@
  * 'virtual' because, as in object-oriented languages, one is supposed
  * here to override them on inheriting classes. On most of
  * inheritances you'll probably want to call the parent's version of
- * the class function too: you must analise each case to tell.
+ * the class function too: you must analyse each case to tell.
  *
  * Take a look at #Elm_Widget_Smart_Data. That's private data bound to
  * each Elementary object @b instance. It aggregates data needed for

diff --git a/src/lib/elm_widget_layout.h b/src/lib/elm_widget_layout.h
index 2f69c53..1cf67bf 100644 (file)
--- a/src/lib/elm_widget_layout.h
+++ b/src/lib/elm_widget_layout.h
@@ -14,7 +14,7 @@
  * other widgets which are, basically, a certain layout with some more
  * logic on top.
  *
- * The idea is make the creation of that widgets as easy as possible,
+ * The idea is to make the creation of that widgets as easy as possible,
  * factorizing code on this common base. For example, a button is a
  * layout (that looks like push button) that happens to react on
  * clicks and keyboard events in a special manner, calling its user
@@ -26,7 +26,7 @@
  * #Elm_Container_Smart_Class. Container parts, here, map directly to
  * Edje parts from the layout's Edje group. Besides that, there's a whole
  * infrastructure around Edje files:
- * - intefacing by signals,
+ * - interfacing by signals,
  * - setting/retrieving text part values,
  * - dealing with table and box parts directly,
  * - etc.