diff options
author | William Jon McCann <william.jon.mccann@gmail.com> | 2014-02-04 18:10:11 -0500 |
---|---|---|
committer | William Jon McCann <william.jon.mccann@gmail.com> | 2014-02-04 18:10:11 -0500 |
commit | 76447c3512f083a11e716d10ade774ade929b2dd (patch) | |
tree | 9c922704e2f46615d10eaee21d5a2bf9b59f6810 /gtk/gtkmain.c | |
parent | a3bad427c7b63357db3d02aa39a291d47af63f6f (diff) | |
download | gtk+-76447c3512f083a11e716d10ade774ade929b2dd.tar.gz |
docs: use quotes instead of <firstterm>
Diffstat (limited to 'gtk/gtkmain.c')
-rw-r--r-- | gtk/gtkmain.c | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/gtk/gtkmain.c b/gtk/gtkmain.c index 44c2fa1140..91966634d4 100644 --- a/gtk/gtkmain.c +++ b/gtk/gtkmain.c @@ -37,16 +37,16 @@ * application in text mode instead. * * Like all GUI toolkits, GTK+ uses an event-driven programming model. When the - * user is doing nothing, GTK+ sits in the <firstterm>main loop</firstterm> and + * user is doing nothing, GTK+ sits in the “main loop” and * waits for input. If the user performs some action - say, a mouse click - then * the main loop "wakes up" and delivers an event to GTK+. GTK+ forwards the * event to one or more widgets. * * When widgets receive an event, they frequently emit one or more - * <firstterm>signals</firstterm>. Signals notify your program that "something + * “signals”. Signals notify your program that "something * interesting happened" by invoking functions you've connected to the signal * with g_signal_connect(). Functions connected to a signal are often termed - * <firstterm>callbacks</firstterm>. + * “callbacks”. * * When your callbacks are invoked, you would typically take some action - for * example, when an Open button is clicked you might display a |