Update README.md

README.md

@@ -20,6 +20,15 @@
   </a>
 </p>
 
+![multi xss](https://image.ibb.co/gR1ToA/Screenshot-2018-10-27-11-18-43.png)
+
+<p align="center">
+  <a href="https://github.com/s0md3v/XSStrike/wiki">XSStrike Wiki</a> •
+  <a href="https://github.com/s0md3v/XSStrike/wiki/Usage">How To Use</a> •
+  <a href="https://github.com/s0md3v/XSStrike/wiki/Compatibility-&-Dependencies">Compatibility</a> •
+  <a href="https://github.com/s0md3v/XSStrike#gallery">Gallery</a>
+</p>
+
 ### Why XSStrike?
 Every XSS scanner out there has a list of payloads, it injectes the payloads and if the payload is reflected into the webpage, it is declared vulnerable but that's just stupid. XSStrike on the other hand analyses the response with multiple parsers and then crafts payloads that are guaranteed to work.
 Here are some examples of the payloads generated by XSStrike:
@@ -36,6 +45,7 @@ Apart from that, XSStrike has crawling, fuzzing, WAF detection capabilities as w
 - Multithreaded crawling
 - Context analysis
 - Configurable Core
+- Highly Researched Workflow
 - WAF detection & evasion
 - Handmade HTML & JavaScript parser
 - Powerful fuzzing engine
@@ -43,7 +53,7 @@ Apart from that, XSStrike has crawling, fuzzing, WAF detection capabilities as w
 - Complete HTTP Support
 - Powered by [Photon](https://github.com/s0md3v/Photon), [Zetanize](https://github.com/s0md3v/zetanize) and [Arjun](https://github.com/s0md3v/Arjun)
 
-### Screenshots
+### Gallery
 #### DOM XSS
 ![dom xss](https://image.ibb.co/d1rpvq/Screenshot-2018-10-27-10-59-43.png)
 #### Reflected XSS