[gupnp] doc: Remove reference to general signal handling

[Jens Georg <jensgeorg src gnome org>]

commit fde1264daa567b0978c8ca56f829de022f77dc2c
Author: Jens Georg <mail jensge org>
Date:   Sat May 10 14:04:46 2014 +0200

    doc: Remove reference to general signal handling
    
    Signed-off-by: Jens Georg <mail jensge org>
    
    https://bugzilla.gnome.org/show_bug.cgi?id=729827

 doc/server-tutorial.xml |   12 ++++--------
 1 files changed, 4 insertions(+), 8 deletions(-)
---
diff --git a/doc/server-tutorial.xml b/doc/server-tutorial.xml
index 8f03295..65a33a9 100644
--- a/doc/server-tutorial.xml
+++ b/doc/server-tutorial.xml
@@ -182,14 +182,10 @@ service = gupnp_device_info_get_service
       value of the variable.
     </para>
     <para>
-      There are two approaches that clients can take to handle these signals.
-      They can either connect a single handler to #GUPnPService::action-invoked
-      or #GUPnPService::query-variable and examine the arguments to decide what
-      action to take.  Alternatively, handlers can be targetted at specific
-      actions or variables by using the <firstterm>signal detail</firstterm>
-      when connecting.  For example, this causes
-      <function>on_get_status_action</function> to be called when the
-      <function>GetStatus</function> action is invoked:
+      Handlers should be targetted at specific actions or variables by using
+      the <firstterm>signal detail</firstterm> when connecting. For example,
+      this causes <function>on_get_status_action</function> to be called when
+      the <function>GetStatus</function> action is invoked:
     </para>
     <programlisting>static void on_get_status_action (GUPnPService *service, GUPnPServiceAction *action, 
gpointer user_data);
 &hellip;