Updated Why should I use this over binary hacking? (markdown)

1 files changed, 1 insertions, 1 deletions

diff --git a/Why-should-I-use-this-over-binary-hacking?.md b/Why-should-I-use-this-over-binary-hacking?.md
index 6f44eff..d2f303b 100644
--- a/Why-should-I-use-this-over-binary-hacking?.md
+++ b/Why-should-I-use-this-over-binary-hacking?.md
@@ -1,6 +1,6 @@
 Binary hacking is, for the most part, very limited. New features are hard to add without the base functionality being present already and tweaked as a result. On top of that, binary files are not readable by humans, unlike to code. While you may pass modified values to some functions, these values don’t necessarily correspond to a specific action. In addition to that, hurdles of debugging and binary patching are often required to even see something different.
 
-The decompilation, on the other hand, allows for the usage of C code to create new functions and edit the game mechanics to one’s liking with more clarity. Some statements in the code are self-explanatory, and unlike binary hacking, modifying the code can serve a person well in real life as it is a valuable skill to use in the industry.
+The decompilation, on the other hand, allows for the use of C code, in writing new functions and editing the game mechanics to one’s liking, with more clarity. Some statements in the code are self-explanatory, and unlike binary hacking, modifying the code can serve a person well in real life as it is a valuable skill to use in the industry.
 
 There is also another, if not _the_ most important advantage to using decompilations: 
 ### **We do not care about offsets.**