Update docs.md

Author: xaitax

docs.md

@@ -4,47 +4,43 @@ title: Docs
 
 # Documentation
 
-welcome to the offcial cSploit documents page.
+Welcome to the offcial cSploit documentations page.
 
 ## Current project status
 
-we are in a delicate first phase of this project, we are not stable. we are moving parts of code into the new core.
-even if you see __release__ this does not mean that it has no bugs.
-my apologies for that, i'm doing my best for achieve a stable app :v:.
+We are in a delicate first phase of this project and we are not stable, yet. Currently we are moving many parts of the code into a new core.
+Even if you see a release marked as __release__, this does not mean that it has no bugs.
+My apologies for that, I'm doing my best to achieve a stable app :v:.
 
-## Errors means
+## Possible error sdsd 
 
-a short error message it's often self-explicative, but sometime what went wrong is too long to explain it in a short message.
-here you can find a description for some common errors.
+A short error message it's often self-explanatory. Sometimes it too difficult to explain an issue with a short message and here you can find a few common exmaples that explain some errors:
 
   - _cannot start process_: this message is printed when the core of cSploit cannot start the required process.
   - _`cmd` returned #`number`_: this message is printed when `cmd` has exited with an error code `number`
   - _`cmd` killed by signal `number`_: this message is printed when `cmd` has been killed by signal `number`
 
-the above errors are bugs, specific for your device. so please report it if no one has already did it.
+The above errors are bugs that are specific for your device. Hence please report them if no one already did.
 
 ## Reporting bugs
 
-i'm human, thus i can fail. this is why we need a good issue tracker as the one provided by github.
-i'm working on an automated way to reporting bugs, directly from the app, just by clicking on a button.
-
-until that day you have to manually collect your logcat and share it on the [github issues page](https://github.com/cSploit/android/issues).
+I'm human, thus i can fail. This is why we need a good issue tracker like the one provided by github.
+I'm working on an automated way of reporting bugs directly from the app just by clicking on a button. Until then you have to manually collect your logcat and share it on the [github issues page](https://github.com/cSploit/android/issues).
 
 ## FAQ
 
-> Q: is cSploit the same as dSploit ?
+> Q: Is cSploit the same as dSploit ?
 > 
-> A: the code is the same, i'm just continuing developing it, but dSploit has been oficcially merge into zANTI2.
+> A: The basic code is the same but I'm continuing the development since dSploit has been oficcially merged into zANTI2.
 
 -----
 
-> Q: when the feature XXX will be implemented or the bug YYY will be solved ?
+> Q: When will feature XYZ implemented or bug ABC fixed?
 > 
-> A: as every open source project: don't ask for ETA :grin:
+> A: Like on every other open source project - don't ask for ETA :grin:
 
 -----
 
-> Q: how can i contribute to cSploit ?
+> Q: How can I contribute to cSploit ?
 > 
-> A: there is many way to contribute, by donating, by improving the source code,
-> by correct my doggish english on this website and so on.
+> A: There are many ways to contribute: by [donating](http://www.csploit.org/donate.html), by improving the source code or by correcting my English on this website.