diff --git a/docs/tursa-user-guide/scheduler.md b/docs/tursa-user-guide/scheduler.md
index d7ca95d..172da93 100644
--- a/docs/tursa-user-guide/scheduler.md
+++ b/docs/tursa-user-guide/scheduler.md
@@ -195,7 +195,7 @@ lists the active QoS on Tursa.
 | standard   | 128                | 48 hrs       | Max. 128 jobs per user | Max. 128 nodes per user, max. 32 jobs per user | gpu, gpu-a100-40, gpu-a100-80, cpu     | Only jobs sizes that are powers of 2 nodes are allowed (i.e. 1, 2, 4, 8, 16, 32 nodes), only available when your budget is positive. |
 | low        | 32                | 24 hrs       | 4           | 4            | gpu, gpu-a100-40, gpu-a100-40, cpu     | Only jobs sizes that are powers of 2 nodes are allowed (i.e. 1, 2, 4, 8, 16, 32 nodes), only available when your budget is zero or negative |
 | high   | 128                | 48 hrs       | Max. 128 jobs per user | Max. 128 nodes per user, max. 32 jobs per user | gpu, gpu-a100-40, gpu-a100-80     | Only jobs sizes that are powers of 2 nodes are allowed (i.e. 1, 2, 4, 8, 16, 32 nodes), only available when you have access to "dpXYZ-high" budget and the budget is positive. Only available to RAC projects. High priority jobs are prioritised above other jobs on the system. |
-| dev        | 2                | 4 hrs       | 2           | 1            | gpu     | For faster turnaround for development jobs and interactive sessions, only available when your budget is positive. The dev QoS only includes A100-40 GPU nodes.  |
+| dev        | 2                | 4 hrs       | 2           | 1            | gpu     | For faster turnaround for development jobs and interactive sessions, only available when your budget is positive. The dev QoS includes 2x A100-40 GPU nodes and 3x A100-80 GPU nodes.  |
 
 You can find out the QoS that you can use by running the following
 command: