mkdb: Make transfer annotation tooltips less ambiguous

1 files changed, 3 insertions, 3 deletions

diff --git a/gtkdoc/mkdb.py b/gtkdoc/mkdb.py
index 87fdf24..1e3bfec 100644
--- a/gtkdoc/mkdb.py
+++ b/gtkdoc/mkdb.py
@@ -150,10 +150,10 @@ AnnotationDefinition = {
     'scope notified': "The callback is valid until the GDestroyNotify argument is called.",
     'set-value-func': "The specified function is used to convert from a struct to a GValue, must be a GTypeInstance.",
     'skip': "Exposed in C code, not necessarily available in other languages.",
-    'transfer container': "Free data container after the code is done.",
+    'transfer container': "The receiver becomes responsible for freeing the data container but not contained items.",
     'transfer floating': "Alias for <acronym>transfer none</acronym>, used for objects with floating refs.",
-    'transfer full': "Free data after the code is done.",
-    'transfer none': "Don't free data after the code is done.",
+    'transfer full': "The receiver becomes responsible for freeing the data.",
+    'transfer none': "The source remains responsible for freeing the data.",
     'type': "Override the parsed C type with given type.",
     'unref-func': "The specified function is used to unref a struct, must be a GTypeInstance.",
     'virtual': "This is the invoker for a virtual method.",