From 23fd1ca9c1e73b9a08d10ff75c9b46a9554e02cd Mon Sep 17 00:00:00 2001
From: Michael Skelton <886344+codingo@users.noreply.github.com>
Date: Mon, 19 Aug 2019 22:40:39 +1000
Subject: [PATCH] Update README.md

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 7dc51bf..2cdc245 100644
--- a/README.md
+++ b/README.md
@@ -84,7 +84,7 @@ Interlace also makes the use of two additional features for controlling executio
 
 These are run on a per-target level. If there are threads available and a blocker is in the way for the current target, Interlace will start commands from the next target within a target list in order to maximise efficiency.
 
-Threads will still multithread per-target, but using these features can allow you to control the execution flow for those targets more directly to prevent commands from running out of order.
+Using these features will allow you to control the execution flow for individual targets more directly in order to prevent commands from running out of order.
 
 ## Blocker
 Blockers prevent anything below them from executing until all commands above them have completed (for the currently active host). For example, in the following: