From f37626b175518b5f62ffcd50f05a96ffdb2d5e1d Mon Sep 17 00:00:00 2001
From: nullableVoidPtr <30564701+nullableVoidPtr@users.noreply.github.com>
Date: Sat, 26 Jan 2019 02:50:10 +0800
Subject: Updated Why should I use this over binary hacking? (markdown)

---
 Why-should-I-use-this-over-binary-hacking?.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

(limited to 'Why-should-I-use-this-over-binary-hacking?.md')

diff --git a/Why-should-I-use-this-over-binary-hacking?.md b/Why-should-I-use-this-over-binary-hacking?.md
index d2f303b..75ac552 100644
--- a/Why-should-I-use-this-over-binary-hacking?.md
+++ b/Why-should-I-use-this-over-binary-hacking?.md
@@ -9,4 +9,4 @@ Unlike binary hacking, one can easily change the size, locations, even the membe
 
 *This is due to the incompleteness of the decompilations; for example, SaveBlock2 cannot be modified as of yet since there are many functions that reference it that are not decompiled.
 
-**Before you start hacking, it is recommended that you have some experience in coding in either: C, C#, Java, Go or Rust if you want to use use the decompilation.**
\ No newline at end of file
+**Before you start hacking, it is recommended that you have some experience in coding in either: C, C#, Java, or any other C-like programming language, if you want to use use the decompilation.**
\ No newline at end of file
-- 
cgit v1.2.3