diff --git a/docs/tutorial/C/gtkmm-tutorial-in.xml b/docs/tutorial/C/gtkmm-tutorial-in.xml
index befc328..ced3568 100644
--- a/docs/tutorial/C/gtkmm-tutorial-in.xml
+++ b/docs/tutorial/C/gtkmm-tutorial-in.xml
@@ -7235,9 +7235,10 @@ mutex or other means of synchronization.
 These interactions arise from the fact that, amongst other things, a
 class inheriting from <classname>sigc::trackable</classname> will, via
 that inheritance, have a <classname>std::list</classname> object
-keeping track of slots representing any of its non-static methods
-(more particularly it keeps a list of callbacks which will null the
-connected slots on its destruction). Each
+keeping track of slots created by calls to
+<function>sigc::mem_fun()</function> representing any of its
+non-static methods (more particularly it keeps a list of callbacks
+which will null the connected slots on its destruction). Each
 <classname>sigc::slot</classname> object also keeps, via
 <classname>sigc::slot_rep</classname>, its own
 <classname>sigc::trackable</classname> object to track any
@@ -7264,12 +7265,6 @@ from <classname>sigc::trackable</classname>, because the effects are
 unintuitive (see particularly points 4 and 5 below).
 </para>
 
-<para>
-The rules for non-static methods apply also for static methods, if
-<function>sigc::mem_fun()</function> is used. It is better to use
-<function>sigc::ptr_fun()</function> for static methods.
-</para>
-
 <orderedlist>
 
 <listitem>
@@ -7308,14 +7303,19 @@ the object.
 
 <listitem>
 <para>
-A <classname>sigc::slot</classname> object which references a
-non-static method of a class deriving from
-<classname>sigc::trackable</classname> should never be copied to
-another thread, nor destroyed by a different thread than the one which
-created it (one consequence of this is that
-<methodname>Glib::Threads::Thread::create()</methodname> should not be called
-with a slot argument which represents a non-static method of such a
-class).
+A <classname>sigc::slot</classname> object created by a call to
+<function>sigc::mem_fun()</function> which references a method of a
+class deriving from <classname>sigc::trackable</classname> should
+never be copied to another thread, nor destroyed by a different thread
+than the one which created it. (One consequence of this is that
+<methodname>Glib::Threads::Thread::create()</methodname> should not be
+called with a slot argument created by a call to
+<function>sigc::mem_fun()</function> which represents a method of such
+a class. It is however safe to pass
+<methodname>Glib::Threads::Thread::create()</methodname> a function
+object representing such a method by using, say,
+<function>boost::bind()</function> or, in C++11,
+<function>std::bind()</function>.)
 </para>
 </listitem>
 
@@ -7324,12 +7324,12 @@ class).
 If a particular class object derives from
 <classname>sigc::trackable</classname>, only one thread should create
 <classname>sigc::slot</classname> objects representing any of the
-class's non-static methods, that is, create slots with
+class's non-static methods by calling
 <function>sigc::mem_fun()</function>. The first thread to create such
 a slot should be regarded as owning the relevant object for the
 purpose of creating further slots referencing <emphasis>any</emphasis>
-of its non-static methods or nulling those slots by disconnecting them
-or destroying the trackable object.
+of its non-static methods using that function, or nulling those slots
+by disconnecting them or destroying the trackable object.
 </para>
 </listitem>
 
