svn commit: r1539673 - /ace/site/trunk/content/user-doc/user-guide.mdtext

[ja...@apache.org]

Author: jawi
Date: Thu Nov  7 15:02:17 2013
New Revision: 1539673

URL: http://svn.apache.org/r1539673
Log:
Minor typo fixed.

Modified:
    ace/site/trunk/content/user-doc/user-guide.mdtext

Modified: ace/site/trunk/content/user-doc/user-guide.mdtext
URL: http://svn.apache.org/viewvc/ace/site/trunk/content/user-doc/user-guide.mdtext?rev=1539673&r1=1539672&r2=1539673&view=diff
==============================================================================
--- ace/site/trunk/content/user-doc/user-guide.mdtext (original)
+++ ace/site/trunk/content/user-doc/user-guide.mdtext Thu Nov  7 15:02:17 2013
@@ -185,7 +185,7 @@ And similar tags on "target-2": 
 
 Under the covers, ACE uses Velocity[^6] to parse the template. This means that, apart from variable substitution, you can also use other Velocity macros and create more complex configurations that might contain conditional sections, loops and other features Velocity provides. See the Velocity documentation for more information on how to use this functionality.
 
-**NOTE**: In case a variable cannot be resolved, it will simply not be replaced, but left as-is. This could lead to invalid or unparsable artifacts on your target!
+In case a variable cannot be resolved, it will simply not be replaced, but left as-is. This could lead to invalid or unparsable artifacts (configuration files) on your target!
 
 ACE will scan all configuration files and replace all known variables as soon as a new deployment is created. This means that for our example, both "target-1" and "target-2" will get a processed version of the configuration file, each with its own specific content. ACE also automatically versions these generated files, to aid downgrading software.