diff --git a/docs.it4i/general/capacity-computing.md b/docs.it4i/general/capacity-computing.md
index 92935fb8d7fbd7aa04e9b09cc74a9203ff06dd17..80e5a53957b66c360bfe1fd8a8fc8b2fe2f0e3bf 100644
--- a/docs.it4i/general/capacity-computing.md
+++ b/docs.it4i/general/capacity-computing.md
@@ -15,11 +15,11 @@ There are two primary scenarios:
 
 1. Numeber of jobs < 1500, **and** the jobs are able to utilize one or more **full** nodes:  
     Use [**Job arrays**][1].  
-    The Job array allows to sumbmit and control many jobs (tasks) in one packet. Several job arrays may be sumitted.
+    The Job array allows to sumbmit and control up to 1500 jobs (tasks) in one packet. Several job arrays may be sumitted.
 
 2. Number of jobs >> 1500, **or** the jobs only utilze a **few cores/accelerators** each:  
     Use [**HyperQueue**][2].  
-    HyperQueue can help efficiently load balance a very large number of (small) jobs amongst available computing nodes.
+    HyperQueue can help efficiently load balance a very large number of jobs (tasks) amongst available computing nodes.
     HyperQueue may be also used if you have dependenices among the jobs.