broker part a bit modified

Submission-flow.md

@@ -27,9 +27,11 @@ Broker gets information about new submission from Web API. At this point broker
 
 1. broker gets message from Web API about new submission
 2. based on information from Web API, broker has to choose suitable worker which matches all submission criteria
-    1. if worker is not working at the moment, broker immediatelly sends job evaluation request to it
-    2. otherwise evaluation request is queued to this particular worker
-3. broker sends evaluation request to worker with all information which was obtained from Web API
+    1. if suitable worker is not found then broker notices Web API about this information and all execution stops
+    2. suitable worker is found
+        1. worker has no jobs at the moment, broker immediatelly sends job evaluation request to it
+        2. otherwise evaluation request is queued to this particular worker and waits until all previous jobs are done
+3. broker sends prepared evaluation request to worker with all information which was obtained from Web API
 
 ## Worker