From 087857156b7eabe7212ee1503104d6f9657ecde7 Mon Sep 17 00:00:00 2001
From: danielsagi <danielsagi2009@gmail.com>
Date: Tue, 24 Jul 2018 17:24:57 +0300
Subject: [PATCH] updated readme file tree

---
 src/README.md | 9 ++++++---
 1 file changed, 6 insertions(+), 3 deletions(-)

diff --git a/src/README.md b/src/README.md
index 316e07f..fe78bd7 100644
--- a/src/README.md
+++ b/src/README.md
@@ -5,14 +5,17 @@ First, lets go through Kube Hunter's basic architecture.
 ### Directory Structure  
 ~~~  
 kube-hunter/  
-        log/  
+        plugins/  
+           # your plugin
         src/  
             core/  
             modules/  
                 discovery/  
                     # your module  
                 hunting/  
-                    # your module  
+                    # your module
+                report/
+                    # your module
         kube-hunter.py  
 ~~~  
 ### Design Pattern   
@@ -176,4 +179,4 @@ If another Hunter subscribes to the events that this Hunter publishes, if can  a
 ## Proving Vulnerabilities  
 The process of proving vulnerabilities, is the base concept of the Active Hunting.    
 To prove a vulnerability, create an `ActiveHunter` that is subscribed to the vulnerability, and inside of the `execute`, specify the `evidence` attribute of the event.   
-*Note that you can specify the 'evidence' attribute without active hunting*  
\ No newline at end of file
+*Note that you can specify the 'evidence' attribute without active hunting*