You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by nf...@apache.org on 2022/10/13 10:29:43 UTC

[camel] branch main updated: fix(doc): Prevent the warning in website build

This is an automated email from the ASF dual-hosted git repository.

nfilotto pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/camel.git


The following commit(s) were added to refs/heads/main by this push:
     new 239400dd079 fix(doc): Prevent the warning in website build
239400dd079 is described below

commit 239400dd0799f7466ccd76e65862548102712f3c
Author: Nicolas Filotto <nf...@talend.com>
AuthorDate: Thu Oct 13 12:29:24 2022 +0200

    fix(doc): Prevent the warning in website build
---
 docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
index 1130591acda..a36c1ec47c3 100644
--- a/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
+++ b/docs/user-manual/modules/ROOT/pages/using-propertyplaceholder.adoc
@@ -220,7 +220,7 @@ context.getPropertiesComponent().setNestedPlaceholder(false);
 
 The property placeholder can be problematic if the double curly brackets are used by a third party library like for example a query in ElasticSearch of type `{"query":{"match_all":{}}}`.
 
-To work around that it is possible to escape the double curly brackets with a backslash character like for example `\{{ property-name \}}`. This way, it won't be interpreted as a property placeholder to resolve and will be resolved as `{{property-name}}`.
+To work around that it is possible to escape the double curly brackets with a backslash character like for example `\{{ property-name \}}`. This way, it won't be interpreted as a property placeholder to resolve and will be resolved as `{{ property-name }}`.
 
 If for some reason, the backslash character before the double curly brackets must not be interpreted as an escape character, it is possible to add another backslash in front of it to escape it, it will then be seen as a backslash.