<!-- ##### FUNCTION g_closure_sink ##### -->
<para>
Takes over the initial ownership of a closure.
-Each closure is initially created in a<firstterm>floating</firstterm> state,
+Each closure is initially created in a <firstterm>floating</firstterm> state,
which means that the initial reference count is not owned by any caller.
g_closure_sink() checks to see if the object is still floating, and if so,
unsets the floating state and decreases the reference count. If the closure
<!-- ##### FUNCTION g_closure_remove_finalize_notifier ##### -->
<para>
-Removes a finalization notifier. Notifiers are automatically removed after
-they are run.
+Removes a finalization notifier.
+</para>
+<para>
+Notice that notifiers are automatically removed after they are run.
</para>
@closure: a #GClosure
<!-- ##### FUNCTION g_closure_remove_invalidate_notifier ##### -->
<para>
-Removes a invalidation notifier. Notifiers are automatically removed after
-they are run.
+Removes an invalidation notifier.
+</para>
+
+<para>
+Notice that notifiers are automatically removed after they are run.
</para>
@closure: a #GClosure
<!-- ##### FUNCTION g_closure_set_marshal ##### -->
<para>
-Sets the marshaller of @closure. The @marshal_data provides a way for a
-meta marshaller to provide additional information to the marshaller.
-(See g_closure_set_meta_marshal().) For GObject's C predefined marshallers
-(the g_cclosure_marshal_*() functions), what it provides is a callback
-function to use instead of @closure->callback.
+Sets the marshaller of @closure. The <literal>marshal_data</literal>
+of @marshal provides a way for a meta marshaller to provide additional
+information to the marshaller. (See g_closure_set_meta_marshal().) For
+GObject's C predefined marshallers (the g_cclosure_marshal_*()
+functions), what it provides is a callback function to use instead of
+@closure->callback.
</para>
@closure: a #GClosure
The same marshallers (generated by
<link linkend="glib-genmarshal">glib-genmarshal</link>) are used everywhere,
but the way that we get the callback function differs. In most cases we want
-to use @closure->callback, but in other cases we want to use use some
-different technique to retrieve the callbakc function.
+to use @closure->callback, but in other cases we want to use some
+different technique to retrieve the callback function.
</para>
<para>
For example, class closures for signals (see g_signal_type_cclosure_new())
</para>
<para>
If the source is not one of the standard GLib types, the @closure_callback
-and @closure_marshal fields of the GSourceFuncs structure must have been
+and @closure_marshal fields of the #GSourceFuncs structure must have been
filled in with pointers to appropriate functions.
</para>