The space appears to trip up the dconv parser and `<var>` is used for other
converters.
---
 doc/configuration.txt | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/doc/configuration.txt b/doc/configuration.txt
index e96a6e199..9b643ebbb 100644
--- a/doc/configuration.txt
+++ b/doc/configuration.txt
@@ -16002,7 +16002,7 @@ secure_memcmp(<var>)
      # value, without leaking the contents using a timing attack.
      acl token_given str(my_secret_token),secure_memcmp(txn.token)
 
-set-var(<var name>)
+set-var(<var>)
   Sets a variable with the input content and returns the content on the output
   as-is. The variable keeps the value and the associated input type. The name 
of
   the variable starts with an indication about its scope. The scopes allowed 
are:
@@ -16308,7 +16308,7 @@ ungrpc(<field_number>,[<field_type>])
   interpret the previous binary sample.
 
 
-unset-var(<var name>)
+unset-var(<var>)
   Unsets a variable if the input content is defined. The name of the variable
   starts with an indication about its scope. The scopes allowed are:
     "proc" : the variable is shared with the whole process
-- 
2.29.0


Reply via email to