From b3758c525600cb622d38e25835c39e1aa80bd9f3 Mon Sep 17 00:00:00 2001 From: Markus Klinik Date: Fri, 24 May 2019 16:45:18 +0200 Subject: [PATCH] wording --- implementation.tex | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/implementation.tex b/implementation.tex index 6234ae4..e815559 100644 --- a/implementation.tex +++ b/implementation.tex @@ -173,10 +173,10 @@ A disadvantage is it does not always find the schedule with the shortest makespa It is sometimes possible to find shorter schedules by changing the order of tasks. Consider the scenario in \cref{fig:greedy-fails}. There are two resources, resource A with one capability capA, and B with one capability capB. -There are three tasks 1, 2, and 3, where task 1 requires capA and tasks 2 and 3 require capB. -Furthermore, task 1 is a predecessor of task 2. +There are the three Tasks 1, 2, and 3, where Task 1 requires capA and Tasks 2 and 3 require capB. +Furthermore, Task 1 is a predecessor of Task 2. There exists exactly one valid assignment, namely the one used in \cref{fig:greedy-fails}. -The greedy schedule builder processes tasks in the order in which they occur, so it fails to see that task 3 could be scheduled at time 0. +The greedy schedule builder processes tasks in the order in which they occur, so it fails to see that Task 3 can be scheduled at time 0. \begin{figure} \centering -- GitLab