[glib/new-gsettings] Some wording changes in the docs

[Matthias Clasen <matthiasc src gnome org>]

commit 6363ddeb76a27666b40c66103495480ca97ea1ac
Author: Matthias Clasen <mclasen redhat com>
Date:   Fri Apr 16 21:39:18 2010 -0400

    Some wording changes in the docs
    
    A few typo fixes included as well.

 gio/gsettings.c |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)
---
diff --git a/gio/gsettings.c b/gio/gsettings.c
index e79841f..92ae788 100644
--- a/gio/gsettings.c
+++ b/gio/gsettings.c
@@ -564,8 +564,8 @@ g_settings_class_init (GSettingsClass *class)
    * The "change-event" signal is emitted once per change event that
    * affects this settings object.  You should connect to this signal
    * only if you are interested in viewing groups of changes before they
-   * are split out into multiple calls to the "changed" signal.  For
-   * most use cases it is more appropriate to use the "changed" signal.
+   * are split out into multiple emissions of the "changed" signal.
+   * For most use cases it is more appropriate to use the "changed" signal.
    *
    * In the event that the change event applies to one or more specified
    * keys, @keys will be an array of #GQuark of length @n_keys.  In the
@@ -612,10 +612,10 @@ g_settings_class_init (GSettingsClass *class)
    * @returns: %TRUE to stop other handlers from being invoked for the
    *           event. FALSE to propagate the event further.
    *
-   * The "writable-change-event" signal is emitted once per wriability
+   * The "writable-change-event" signal is emitted once per writability
    * change event that affects this settings object.  You should connect
    * to this signal if you are interested in viewing groups of changes
-   * before they are split out into multiple calls to the
+   * before they are split out into multiple emissions of the
    * "writable-changed" signal.  For most use cases it is more
    * appropriate to use the "writable-changed" signal.
    *
@@ -624,7 +624,7 @@ g_settings_class_init (GSettingsClass *class)
    * that the writability change affects the entire settings object,
    * @key will be 0.
    *
-   * The default handler for this signal invokes the "writabile-changed"
+   * The default handler for this signal invokes the "writable-changed"
    * and "changed" signals for each affected key.  This is done because
    * changes in writability might also imply changes in value (if for
    * example, a new mandatory setting is introduced).  If any other