[glib] Fix typos in gbytes_hash and g_time_zone_find_interval docs



commit d67813045dfd6336a6e109c4818990c3fb117ade
Author: Gergely POLONKAI <gergely polonkai eu>
Date:   Sat Jul 12 07:36:00 2014 +0000

    Fix typos in gbytes_hash and g_time_zone_find_interval docs
    
    https://bugzilla.gnome.org/show_bug.cgi?id=733084

 glib/gbytes.c    |    2 +-
 glib/gtimezone.c |    2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)
---
diff --git a/glib/gbytes.c b/glib/gbytes.c
index a22500b..1520d76 100644
--- a/glib/gbytes.c
+++ b/glib/gbytes.c
@@ -346,7 +346,7 @@ g_bytes_equal (gconstpointer bytes1,
  *
  * Creates an integer hash code for the byte data in the #GBytes.
  *
- * This function can be passed to g_hash_table_new() as the @key_equal_func
+ * This function can be passed to g_hash_table_new() as the @key_hash_func
  * parameter, when using non-%NULL #GBytes pointers as keys in a #GHashTable.
  *
  * Returns: a hash value corresponding to the key.
diff --git a/glib/gtimezone.c b/glib/gtimezone.c
index 1c1d84c..b61529f 100644
--- a/glib/gtimezone.c
+++ b/glib/gtimezone.c
@@ -1699,7 +1699,7 @@ g_time_zone_adjust_time (GTimeZone *tz,
  * If @type is %G_TIME_TYPE_UNIVERSAL then this function will always
  * succeed (since universal time is monotonic and continuous).
  *
- * Otherwise @time_ is treated is local time.  The distinction between
+ * Otherwise @time_ is treated as local time.  The distinction between
  * %G_TIME_TYPE_STANDARD and %G_TIME_TYPE_DAYLIGHT is ignored except in
  * the case that the given @time_ is ambiguous.  In Toronto, for example,
  * 01:30 on November 7th 2010 occurred twice (once inside of daylight


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]