X-Git-Url: https://git.teslayout.com/public/public/public/?p=anna.git;a=blobdiff_plain;f=example%2Fdiameter%2Flauncher%2Fdeployments%2Fft-client%2FREADME;h=296822fab15922937a6c5e762ad91dba659067f5;hp=7255a7f3e5681a14460072f203fcf5156464ae98;hb=ea1b80f8fd0c1b806460f98f4e4cf433698857d9;hpb=7bf36f6cec41494071f07699184d8230ccd8cb41

diff --git a/example/diameter/launcher/deployments/ft-client/README b/example/diameter/launcher/deployments/ft-client/README
index 7255a7f..296822f 100644
--- a/example/diameter/launcher/deployments/ft-client/README
+++ b/example/diameter/launcher/deployments/ft-client/README
@@ -1,8 +1,8 @@
 ABOUT CONTENT
 -------------
-Template for xml messages (message.dtd) and dictionaries (dictionary.dtd) are informative, not
-actually required by process. They are located at './DTDs'. Stacks are available at './stacks'.
-There are also some stuff (hex/xml examples, etc.) which could be useful.
+Template for xml messages (message.dtd), dictionaries (dictionary.dtd) and services (services.dtd)
+are informative, not actually required by process. They are located at './DTDs'. Stacks are available
+at './stack_examples'. There are also some stuff (hex/xml examples, etc.) which could be useful.
 
 The directory 'tests' contains resources to create FT test cases. The script 'common.sh' implement
 a basic scheduler to launch a request to the server, waits for incoming activity, retrieve the
@@ -13,17 +13,13 @@ client executable (for example we could define an incoming handler in different
 represent different test cases, linking them to a common simple diameter client agent). But with
 this simple scripts we could do something valid to start with.
 
-Additional helpers/scripts could be found at './resources' directory.
-
 STARTING THE PROCESS
 --------------------
 Launch the executable process without arguments to see a complete command-line help.
-Don't be scared. There are plenty of possibilities but the 'run.sh' script has been prepared
-for the type of launcher you wanted.
+Don't be scared. There are plenty of possibilities but the 'run.sh' script and 'services.xml'
+have been prepared for the type of launcher you wanted.
 
 OPERATION
 ---------
 Management interface for this version is based on SIGUSR2 signal caugh. Use './operation.sh'
-script to send any operation to the process. Ask for help with that script to see all the
-operations supported.
-
+script to send any operation to the process. Check 'HELP.md' for more information.