query_module: modules are separated by ';'

doc/reference.texi

@@ -703,7 +703,7 @@ The @code{zones} statement contains definition of zones served by Knot DNS.
     [ @code{notify-in} @kbd{remote_id} [, @kbd{remote_id}, @dots{} ]@code{;} ]
     [ @code{notify-out} @kbd{remote_id} [, @kbd{remote_id}, @dots{} ]@code{;} ]
     [ @code{update-in} @kbd{remote_id} [, @kbd{remote_id}, @dots{} ]@code{;} ]
-    [ @code{query_module} @code{@{} @kbd{module_name} @code{"}@kbd{string}@code{"} [, @kbd{module_name} @code{"}@kbd{string}@code{"}, @dots{} ] @code{@}} ]
+    [ @code{query_module} @code{@{} @kbd{module_name} @code{"}@kbd{string}@code{"}@code{;} [ @kbd{module_name} @code{"}@kbd{string}@code{"}; @dots{} ] @code{@}} ]
     [ @kbd{zone_options} ]
   @code{@}}
 @code{@}}

man/knot.conf.5.in

@@ -373,8 +373,8 @@ serves as an example of the configuration for knotc(8) and knotd(8).
 	# Query modules are dynamically loaded modules that can alter query plan
 	# Configuration is always module-specific, but passed as a simple string
 	query_module {
-		module_one "configuration string",
-		module_two "specific configuration string"
+		module_one "configuration string";
+		module_two "specific configuration string";
 	}
   }
  }

samples/knot.full.conf

@@ -369,8 +369,8 @@ zones {
 	# Query modules are dynamically loaded modules that can alter query plan processing
 	# Configuration is always module-specific, but passed as a simple string here 
 	query_module {
-		module_one "configuration string",
-		module_two "specific configuration string"
+		module_one "configuration string";
+		module_two "specific configuration string";
 	}
   }
 }

src/knot/conf/cf-parse.y

@@ -845,8 +845,6 @@ query_module:
  ;
 
 query_module_list:
-   query_module
- | query_module ',' query_module_list
  | query_module ';' query_module_list
  ;