[glib] gstrfuncs: Use curly quotes in a documentation comment

[Philip Withnall <pwithnall src gnome org>]

commit 880f07f94cdee87b66543b64acad9540060e5d38
Author: Philip Withnall <withnall endlessm com>
Date:   Mon Nov 13 10:37:11 2017 +0000

    gstrfuncs: Use curly quotes in a documentation comment
    
    Nobody can argue with this: the documentation comment is about, and
    contains, Unicode accents.
    
    Signed-off-by: Philip Withnall <withnall endlessm com>

 glib/gstrfuncs.c |   10 +++++-----
 1 files changed, 5 insertions(+), 5 deletions(-)
---
diff --git a/glib/gstrfuncs.c b/glib/gstrfuncs.c
index 48b05c1..e7240b6 100644
--- a/glib/gstrfuncs.c
+++ b/glib/gstrfuncs.c
@@ -3095,11 +3095,11 @@ g_str_tokenize_and_fold (const gchar   *string,
  * call g_str_tokenize_and_fold() on the search term and
  * perform lookups into that index.
  *
- * As some examples, searching for "fred" would match the potential hit
- * "Smith, Fred" and also "Frédéric".  Searching for "Fréd" would match
- * "Frédéric" but not "Frederic" (due to the one-directional nature of
- * accent matching).  Searching "fo" would match "Foo" and "Bar Foo
- * Baz", but not "SFO" (because no word has "fo" as a prefix).
+ * As some examples, searching for ‘fred’ would match the potential hit
+ * ‘Smith, Fred’ and also ‘Frédéric’.  Searching for ‘Fréd’ would match
+ * ‘Frédéric’ but not ‘Frederic’ (due to the one-directional nature of
+ * accent matching).  Searching ‘fo’ would match ‘Foo’ and ‘Bar Foo
+ * Baz’, but not ‘SFO’ (because no word has ‘fo’ as a prefix).
  *
  * Returns: %TRUE if @potential_hit is a hit
  *