Updated syntax to new append for --variable

Author: ArneTR

content/en/docs/measuring/runner-switches.md

@@ -18,8 +18,9 @@ Apart from the `config.yml` some additional configuration is possible when manua
     * Duplicated filenames are allowed (if you want to repeat the same file(s) multiple times, consider using `--iterations`)
   + Relative paths are supported, e.g. "../usage_scenario.yml"
   + Wildcard characters '\*' and '?' are supported, e.g. "*.yml" (all yml files in the current directory are executed sequentially)
-- `--variables` A list of string key-value pairs with variables to be replaced in the [usage_scenario.yml →]({{< relref "usage-scenario" >}})
-  + e.g.: `--variables '__GMT_VAR_MY_VALUE_=cats are cool'`
+- `--variable` A key-value pair with a variable to be replaced in the [usage_scenario.yml →]({{< relref "usage-scenario" >}})
+  + e.g.: `--variable '__GMT_VAR_MY_VALUE_=cats are cool'`
+  + Can be used multiple times if more than one variable shall be submitted
 - `--commit-hash-folder` Use a different folder than the repository root to determine the commit hash for the run
 - `--user-id` Execute run as a specific user (Default: 1) - See also [User Management →]({{< relref "/docs/cluster/user-management.md" >}})
 - `--config-override` Override the configuration file with the passed in yml file.

content/en/docs/measuring/usage-scenario.md

@@ -346,7 +346,7 @@ The reason being that when your variable contains *YAML* control characters like
 A run where we want the variable to be *1* as example can be started like this:
 
 ```bash
-python3 runner.py --uri PATH_TO_SCENARIO --variables "__GMT_VAR_DURATION__=1"
+python3 runner.py --uri PATH_TO_SCENARIO --variable "__GMT_VAR_DURATION__=1"
 ```
 
 See more details in [Runner switches →]({{< relref "/docs/measuring/runner-switches" >}})