From 180957e93c70b38c92efc4920dd05d447f0eef88 Mon Sep 17 00:00:00 2001
From: tetraxile <64417119+tetraxile@users.noreply.github.com>
Date: Sun, 30 Jun 2024 10:55:06 +0100
Subject: [PATCH] docs: fix cheatsheet link (#125)

---
 Contributing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Contributing.md b/Contributing.md
index 2360d44..0971a0d 100644
--- a/Contributing.md
+++ b/Contributing.md
@@ -58,7 +58,7 @@ CLion interacts with CMake directly, so you need to make sure CLion's build prof
     * Understanding the function is very important.
     * Rename variables, add structures, do everything you can to make the output as clean as possible.
     * C++ code tends to make heavy use of inline functions. For example, inlined string comparisons or copies are very common and tend to obscure what the function does. Focus on the outline of the function.
-    * The [cheatsheet](https://github.com/zeldaret/botw/blob/master/Cheatsheet.md) (of the BotW project) might help you recognize inline functions.
+    * The [cheatsheet](https://botw.link/cheatsheet) (of the BotW project) might help you recognize inline functions.
 
 3. **Implement the function in C++.**
     * Stay close to the original code, but not too close: your code should mostly look like normal, clean C++ code. If it does not, chances are that you won't get a good match at all.