diff --git a/docs/clearml_agent.md b/docs/clearml_agent.md
index 6303a923..561bdc31 100644
--- a/docs/clearml_agent.md
+++ b/docs/clearml_agent.md
@@ -487,7 +487,7 @@ An agent can be spun on multiple GPUs (e.g. 8 GPUs, `--gpus 0-7`), and then atta
 queues that are configured to run with a certain amount of resources:
 
 ```console
-clearml-agent daemon --dynamic-gpus --queues quad_gpu=4 dual_gpu=2 
+clearml-agent daemon --dynamic-gpus --gpus 0-7 --queue quad_gpu=4 dual_gpu=2 
 ``` 
 
 The agent can now spin multiple Tasks from the different queues based on the number of GPUs configured to the queue.
@@ -497,7 +497,7 @@ queue, look for available GPUs again and spin on GPUs 4-5.
 Another option for allocating GPUs:
 
 ```console
-clearml-agent daemon --dynamic-gpus --queue dual=2 opportunistic=1-4
+clearml-agent daemon --dynamic-gpus --gpus 0-7 --queue dual=2 opportunistic=1-4
 ``` 
 
 Notice that a minimum and maximum value of GPUs was specified for the `opportunistic` queue. This means the agent
diff --git a/docs/references/clearml_agent_ref.md b/docs/references/clearml_agent_ref.md
index 0f0597ea..354edd81 100644
--- a/docs/references/clearml_agent_ref.md
+++ b/docs/references/clearml_agent_ref.md
@@ -213,7 +213,7 @@ Use the `daemon` subcommand to run a worker, optionally in a Docker container, l
 
 **`dynamic-gpus`**
 
-*  Allow to dynamically allocate gpus based on queue properties, configure with `--queues <queue_name>=<num_gpus>`.
+*  Allow to dynamically allocate gpus based on queue properties, configure with `--queue <queue_name>=<num_gpus>`.
 
   For example: `--dynamic-gpus --queue dual_gpus=2 single_gpu=1`