From 70fdde32ba430f7e29346b4783c978aad4b9898e Mon Sep 17 00:00:00 2001
From: Michael Skelton <886344+codingo@users.noreply.github.com>
Date: Sun, 6 Jan 2019 18:09:42 +1000
Subject: [PATCH] Fix CIDR notation example

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

diff --git a/README.md b/README.md
index 07089ed..9d728ff 100644
--- a/README.md
+++ b/README.md
@@ -108,7 +108,7 @@ Interlace automatically expands CIDR notation when starting threads (unless the
 
 To run a virtual host scan against every target within 192.168.12.0/24 using a direct command you could use:
 ```bash
-interlace -t 192.168.12.0/24 -c "vhostscan $target -oN $output/$target-vhosts.txt" -o ~/scans/ -threads 50
+interlace -t 192.168.12.0/24 -c "vhostscan _target_ -oN _output_/_target_-vhosts.txt" -o ~/scans/ -threads 50
 ```
 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.