Merge pull request cSploit#3 from Interneedus/patch-1

Update index.md

Author: fabinhojcr

index.md

@@ -22,7 +22,7 @@ My final goal is to write an application that is able to:
 
 Thanks to the new core, cSploit will be easily portable.
 
-Basically it can run on any UNIX-based system, but for now only andorid is supported. When I reach a beta-state version i will consider working on iOS, OSX, GTK+ and QT.
+Basically it can run on any UNIX-based system, but for now only andorid is supported. When I reach a beta-state version I will consider working on iOS, OSX, GTK+ and QT.
 
 ### Contribute to the code
 
@@ -31,39 +31,39 @@ If you actively contribute to the project I will ask you to join the team.
 
 ### Support us
 
-please [donate](/donate.html) to cSpoit to support our efforts and resources.
+Please [donate](/donate.html) to cSpoit to support our efforts and resources.
 Thank you :heart:
 
-### story
+### Story
 
 After being initially created by evilsocket, I ( tux-mind ) started working on dSploit in summer 2012, i forked it and added the following features:
 
-  - vulnerability finder
-  - exploit finder
+  - Vulnerability finder
+  - Exploit finder
   - MetaSploitFramework integration ( draft )
 
-after some weeks the project owner ( evilsocket ) asked me to merge it to the upstream branch.
-initially we were about 2 main developers ( me and evilsocket ) and an UI developer ( androguide ).
-after a few months evilsocket get overloaded by work and stop working on it.
+After some weeks the project owner ( evilsocket ) asked me to merge it to the upstream branch.
+Initially there were about 2 main developers (me and evilsocket) and an UI developer ( androguide ).
+After a few months evilsocket got overloaded by work and stop working on it.
 
 
-but i kept working on dSploit, always trying to improve it.
-many function were slow and error-prone, i changed the way them work, added new features and correct many bugs.
+But I kept working on dSploit, always trying to improve it.
+Many functions were slow and error-prone, I changed the way them work, added new features and corrected many bugs.
 
 
-finally, in summer 2014 i suggested a new way to make dSploit work, the new core.
-basically i wish to move all the slow and inefficent code out of Java.
-evilsocket agree with my suggestion and told me to start working on it.
-evilsocket were very busy with work because he started working for zImpremium.
+Finally, in summer 2014 I suggested a new way to make dSploit work, the new core.
+basically I wish to move all the slow and inefficent code out of Java.
+Evilsocket agreed with my suggestion and told me to start working on it.
+Evilsocket is very busy with work because he started working for zImpremium.
 
 
-on autumn 2014 evilsocket received the order to merge dSploit into zANTI2.
+On autumn 2014 evilsocket received the order to merge dSploit into zANTI2.
 this decision killed the project.
-i asked if i could bring it on, but evilsocket told that the domain dsploit.net belongs to him 
-and dsploit will oficially merge into zANTI2.
-so i forked the project and finished my work on the new core.
+I asked if I could bring it on, but evilsocket told that the domain dsploit.net belongs to him 
+and dsploit will officially merge into zANTI2.
+so I forked the project and finished my work on the new core.
 
-> **NOTE:** evilsocket told, that in a far future zANTI2 will be open source,
+> **NOTE:** Evilsocket told, that in a far future zANTI2 will be open source,
 > but I don't want to wait for this, I want to finish all original dSploit TODOs.
 
 This was when cSploit was born.