From ff2b5d33834055958d53dd8e8e3cc1acd13e6eba Mon Sep 17 00:00:00 2001 From: Simon McVittie Date: Thu, 5 Apr 2018 11:22:33 +0100 Subject: [PATCH] Spelling: Fix spelling of "similarly" Detected by Debian's Lintian tool. Signed-off-by: Simon McVittie --- docs/reference/gio/gdbus-codegen.xml | 2 +- gio/gdbusconnection.c | 2 +- gio/gunionvolumemonitor.c | 2 +- 3 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/reference/gio/gdbus-codegen.xml b/docs/reference/gio/gdbus-codegen.xml index e4192084d..6fd091f42 100644 --- a/docs/reference/gio/gdbus-codegen.xml +++ b/docs/reference/gio/gdbus-codegen.xml @@ -869,7 +869,7 @@ my_app_frobber_proxy_new_sync (GDBusConnection *connection, subclass. For example, to handle HelloWorld() method invocations, set the vfunc for handle_hello_hello_world() in the - MyAppFrobberIface structure. Similary, to handle + MyAppFrobberIface structure. Similarly, to handle the net.Corp.MyApp.Frobber:Verbose property override the :verbose #GObject property from the subclass. To emit a signal, use diff --git a/gio/gdbusconnection.c b/gio/gdbusconnection.c index 543ca0b2d..7270365b6 100644 --- a/gio/gdbusconnection.c +++ b/gio/gdbusconnection.c @@ -3088,7 +3088,7 @@ static volatile guint _global_filter_id = 1; * dispatched anywhere else - not even the standard dispatch machinery * (that API such as g_dbus_connection_signal_subscribe() and * g_dbus_connection_send_message_with_reply() relies on) will see the - * message. Similary, if a filter consumes an outgoing message, the + * message. Similarly, if a filter consumes an outgoing message, the * message will not be sent to the other peer. * * If @user_data_free_func is non-%NULL, it will be called (in the diff --git a/gio/gunionvolumemonitor.c b/gio/gunionvolumemonitor.c index 8e58d18ed..eeb4c5ffc 100644 --- a/gio/gunionvolumemonitor.c +++ b/gio/gunionvolumemonitor.c @@ -621,7 +621,7 @@ _g_mount_get_for_mount_path (const gchar *mount_path, * also listen for the "removed" signal on the returned object * and give up its reference when handling that signal * - * Similary, if implementing g_volume_monitor_adopt_orphan_mount(), + * Similarly, if implementing g_volume_monitor_adopt_orphan_mount(), * the implementor must take a reference to @mount and return it in * its g_volume_get_mount() implemented. Also, the implementor must * listen for the "unmounted" signal on @mount and give up its