Update (Martin's comments)

Rewritten-docs.md

@@ -669,7 +669,6 @@ First, write header of the job to the configuration file.
 ```{.yml}
 submission:
     job-id: hello-word-job
-    language: c
     file-collector: http://localhost:9999/exercises
     hw-groups:
         - group1
@@ -685,10 +684,10 @@ _source.c_ (if submitted by user) already available in working directory, so
 just call the GCC. Compilation is run in sandbox as any other external program
 and should have relaxed time and memory limits. In this scenarion, worker
 defaults are used. If compilation fails, whole job is immediately terminated
-(_fatal-failure_ bit set). Because _chdir_ and _bound-directories_ options in
+(_fatal-failure_ bit set). Because _bound-directories_ option in sandbox limits
-sandbox limits section are mostly common for all tasks, they can be set in
+section is mostly common for all tasks, it can be set in worker configuration
-worker configuration instead of job configuration (suppose this for following
+instead of job configuration (suppose this for following tasks). For
-tasks). For configuration of workers please contact your administrator.
+configuration of workers please contact your administrator.
 
 ```{.yml}
 - task-id: "compilation"
@@ -723,7 +722,6 @@ frontend.
   test-id: "A"
   type: "execution"
   priority: 2
-  fatal-failure: false
   dependencies:
       - compilation
   cmd:
@@ -733,6 +731,7 @@ frontend.
 	  stdout: ${EVAL_DIR}/out.txt
       limits:
           - hw-group-id: group1
+            chdir: ${EVAL_DIR}
             time: 0.5
             memory: 8192
 ```
@@ -773,5 +772,6 @@ or not (other). Worker default limits are used.
       name: "isolate"
       limits:
           - hw-group-id: group1
+            chdir: ${EVAL_DIR}
 ```