summaryrefslogtreecommitdiff
path: root/gtk
diff options
context:
space:
mode:
authorStefan Sauer <ensonic@users.sf.net>2013-05-03 20:39:24 +0200
committerStefan Sauer <ensonic@users.sf.net>2013-05-03 20:40:00 +0200
commitb8366027b3de1b04f2739eb2db3eaf27ad75fe7a (patch)
treec4b1ac2ada7c09dad7301191e882b1285d715118 /gtk
parent41bf557012a06544bfe73ab3c72abbeba556a438 (diff)
downloadgtk+-b8366027b3de1b04f2739eb2db3eaf27ad75fe7a.tar.gz
widget: fix two typos in api-docs
Diffstat (limited to 'gtk')
-rw-r--r--gtk/gtkwidget.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/gtk/gtkwidget.c b/gtk/gtkwidget.c
index 78fc44db3f..c0da4d04ee 100644
--- a/gtk/gtkwidget.c
+++ b/gtk/gtkwidget.c
@@ -4799,10 +4799,10 @@ static guint tick_callback_id;
* @user_data: data to pass to @callback
* @notify: function to call to free @user_data when the callback is removed.
*
- * Queues a animation frame update and adds a callback to be called
+ * Queues an animation frame update and adds a callback to be called
* before each frame. Until the tick callback is removed, it will be
* called frequently (usually at the frame rate of the output device
- * or as quickly as the application an be repainted, whichever is
+ * or as quickly as the application can be repainted, whichever is
* slower). For this reason, is most suitable for handling graphics
* that change every frame or every few frames. The tick callback does
* not automatically imply a relayout or repaint. If you want a