From 20173468318b1e5677d94244246ea2d0d3a00803 Mon Sep 17 00:00:00 2001
From: Michael Skelton <886344+codingo@users.noreply.github.com>
Date: Fri, 26 Oct 2018 12:51:17 +1000
Subject: [PATCH] Update README.md

---
 README.md | 11 ++++++-----
 1 file changed, 6 insertions(+), 5 deletions(-)

diff --git a/README.md b/README.md
index 436abb8..8633f94 100644
--- a/README.md
+++ b/README.md
@@ -44,13 +44,14 @@ interlace -t 192.168.12.0/24 -c "vhostscan $target -oN $output/$target-vhosts.tx
 This is despite VHostScan not having any inbuilt CIDR notation support. Since Interlace expands the notation before building a queue of threads, VHostScan for all intents is only receiving a list of direct IP addresses to scan.
 
 ## Threading Support for an application that doesn't support it
-Run a [virtual host scan](https://github.com/codingo/VHostScan) against each host in a file (target-lst.txt), whilst also limiting scans at any one time to 50 maximum threads:
-### Example 1 - direct command
+Run a [virtual host scan](https://github.com/codingo/VHostScan) against each host in a file (target-lst.txt), whilst also limiting scans at any one time to 50 maximum threads.
+
+This could be done using a direct command:
 ```bash
 interlace -tL ./target-list.txt -c "vhostscan -t $target -oN $output/$target-vhosts.txt" -o ~/scans/ -threads 50
 ```
-### Example 2- command file
-To run the same command as above, but using a command file, this would be done using:
+
+Or, alternatively, to run the same command as above, but using a command file, this would be done using:
 ```bash
 interlace -cL ./vhosts-commands.txt -tL ./target-list.txt -threads 50 -o ~/scans
 ```
@@ -59,4 +60,4 @@ This presumes that the contents of the command file is:
 vhostscan -t $target -oN $output/$target-vhosts.txt
 ```
 
-This would output a file for each target in the specified output folder.
+This would output a file for each target in the specified output folder. You could also run multiple commands simply by adding them into the command file.