--- a/buildframework/helium/sf/java/signaling/signalingCreateANewSignal.rst	Wed Sep 29 17:48:06 2010 +0100
+++ b/buildframework/helium/sf/java/signaling/signalingCreateANewSignal.rst	Sun Oct 10 15:22:15 2010 +0300
@@ -69,7 +69,7 @@
 
 The signalListenerConfig defines which target to listen and raise signal for. The target name is defined through the **target** attribute.
 Then the nested **targetCondition** element is used to configure how the signal should be triggered.
-This element accepts any nested `Ant conditions <http://ant.apache.org/manual/CoreTasks/conditions.html>`_.
+This element accepts any nested `Ant conditions <http://ant.apache.org/manual/Tasks/condition.html>`_.
 In this case the signal will get raised only if the file is not present after the execution of the **custom-action** target.
 
 The framework then uses the defined signalInput from the signalNotifierInput configuration to know how to behave when the signal is raised. In the previous example it will