summaryrefslogtreecommitdiff
path: root/gtk/gtkdialog.c
diff options
context:
space:
mode:
authorWilliam Jon McCann <william.jon.mccann@gmail.com>2014-02-07 13:32:47 -0500
committerWilliam Jon McCann <william.jon.mccann@gmail.com>2014-02-07 13:32:47 -0500
commite34bd4137d4fba33b2cbea927fdcc829b1983aaa (patch)
treea75585038e3a419a4aa3383233450c5ba3fe2c83 /gtk/gtkdialog.c
parentf0000b2f3d3de91a1814d3e243a0e0a301c9f255 (diff)
downloadgtk+-e34bd4137d4fba33b2cbea927fdcc829b1983aaa.tar.gz
docs: use apostrophes in *n't
Diffstat (limited to 'gtk/gtkdialog.c')
-rw-r--r--gtk/gtkdialog.c6
1 files changed, 3 insertions, 3 deletions
diff --git a/gtk/gtkdialog.c b/gtk/gtkdialog.c
index e5b2c03c2f..bbc13203c8 100644
--- a/gtk/gtkdialog.c
+++ b/gtk/gtkdialog.c
@@ -946,7 +946,7 @@ gtk_dialog_add_action_widget (GtkDialog *dialog,
* clicking the button will emit the #GtkDialog::response signal with
* the given @response_id. The button is appended to the end of the
* dialog’s action area. The button widget is returned, but usually
- * you don't need it.
+ * you don’t need it.
*
* Return value: (transfer none): the #GtkButton widget that was added
**/
@@ -1216,7 +1216,7 @@ run_destroy_handler (GtkDialog *dialog, gpointer data)
* will be modal. You can force gtk_dialog_run() to return at any time by
* calling gtk_dialog_response() to emit the ::response signal. Destroying
* the dialog during gtk_dialog_run() is a very bad idea, because your
- * post-run code won't know whether the dialog was destroyed or not.
+ * post-run code won’t know whether the dialog was destroyed or not.
*
* After gtk_dialog_run() returns, you are responsible for hiding or
* destroying the dialog if you wish to do so.
@@ -1368,7 +1368,7 @@ gtk_dialog_get_widget_for_response (GtkDialog *dialog,
* of a dialog.
*
* Returns: the response id of @widget, or %GTK_RESPONSE_NONE
- * if @widget doesn't have a response id set.
+ * if @widget doesn’t have a response id set.
*
* Since: 2.8
*/