Centralize ADML deployment

[anna.git] / example / diameter / launcher / deployments / advanced / README

diff --git a/example/diameter/launcher/deployments/advanced/README b/example/diameter/launcher/deployments/advanced/README
index 3b59438..404524b 100644 (file)
--- a/example/diameter/launcher/deployments/advanced/README
+++ b/example/diameter/launcher/deployments/advanced/README
@@ -1,7 +1,7 @@
 
 ABOUT CONTENT
 -------------
-Stacks available at './stacks'. The launcher uses 'dictionary.xml' created ad-hoc by default.
+Stacks at './stack_examples'. The launcher uses 'dictionary.xml' created ad-hoc by default.
 It is a QoS application dictionary.
 
 Template for xml messages (message.dtd), dictionaries (dictionary.dtd) and services (services.dtd)
@@ -10,13 +10,12 @@ are informative, not actually required by process. Located at './DTDs'.
 STARTING THE PROCESS
 --------------------
 Start with 'run.sh'. You could manually edit such script adding parameters as '--trace debug' to
-get complete 'launcher.trace'. Execute 'ADML-launcher' without arguments to see a complete
-command-line help.
+get complete 'launcher.trace'. Execute 'ADML' without arguments to see a complete command-line help.
 
 DEPLOYED SCRIPTS
 ----------------
 You could get help about installed resources by mean 'help.sh', which launch a help request to
-the started ADML-launcher process http interface. All the implemented http operations could be
-launched through a script to make easy use. The http client 'curl' is used by default due to
-its presence on common linux distributions.
+the started ADML process http interface. All the implemented http operations could be launched
+through a script to make easy use. The http client 'curl' is used by default due to its presence
+on common linux distributions.