From 4b9a87e0f83ddebff166acb90755bf77306bf7db Mon Sep 17 00:00:00 2001 From: LagoLunatic Date: Sun, 23 Aug 2026 14:32:27 -0400 Subject: [PATCH] Fix bad relative markdown links --- CONTRIBUTING.md | 2 +- README.md | 2 +- docs/decompiling.md | 4 ++-- 3 files changed, 4 insertions(+), 4 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 6cc0080c6..91982a70d 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -1,5 +1,5 @@ # Contributing -Anyone can open a pull request, but please be aware that we do not accept contributions that are primarily AI-generated or directly copy-pasted from Ghidra. Your PR will be closed if it contains obvious signs of machine-generated code. It is your responsibility to check the code that you are submitting and make sure it is readable and feels like something a human programmer would write. Refer to the [coding guidelines page](coding_guidelines.md) for more information. +Anyone can open a pull request, but please be aware that we do not accept contributions that are primarily AI-generated or directly copy-pasted from Ghidra. Your PR will be closed if it contains obvious signs of machine-generated code. It is your responsibility to check the code that you are submitting and make sure it is readable and feels like something a human programmer would write. Refer to the [coding guidelines page](/docs/coding_guidelines.md) for more information. Check the [readme](/README.md) for details on how to get the repository set up, and the [decompiling guide](/docs/decompiling.md) for an explanation of the process of decompiling itself. diff --git a/README.md b/README.md index 8dcc9502f..0342deee7 100644 --- a/README.md +++ b/README.md @@ -122,4 +122,4 @@ Contributing If you've got all the requirements set up and want to learn how to contribute to the decompilation effort, see [this guide](/docs/decompiling.md) for details. -Anyone can open a pull request, but please be aware that we do not accept contributions that are primarily AI-generated or directly copy-pasted from Ghidra. Your PR will be closed if it contains obvious signs of machine-generated code. It is your responsibility to check the code that you are submitting and make sure it is readable and feels like something a human programmer would write. Refer to the [coding guidelines page](coding_guidelines.md) for more information. +Anyone can open a pull request, but please be aware that we do not accept contributions that are primarily AI-generated or directly copy-pasted from Ghidra. Your PR will be closed if it contains obvious signs of machine-generated code. It is your responsibility to check the code that you are submitting and make sure it is readable and feels like something a human programmer would write. Refer to the [coding guidelines page](/docs/coding_guidelines.md) for more information. diff --git a/docs/decompiling.md b/docs/decompiling.md index 8450b33e1..5eaab4cca 100644 --- a/docs/decompiling.md +++ b/docs/decompiling.md @@ -4,7 +4,7 @@ This document describes the basics how to start decompiling code and contributin If you haven't already, you should first follow the instructions in the [readme](../README.md) to get the decomp set up, as well as the tools you will be using to work on it: objdiff and Ghidra. -You should also read the [coding guidelines page](coding_guidelines.md) page to ensure that the code you write is clear and readable. +You should also read the [coding guidelines page](/docs/coding_guidelines.md) page to ensure that the code you write is clear and readable. ## Table of Contents @@ -691,4 +691,4 @@ Then you can just submit a pull request as-is instead of worrying about it any m Once an actor is fully decompiled, you can start naming some of its member variables if you want to. This is completely optional - it's normal to submit a PR without documenting most fields. Leaving them unnamed (e.g. `field_0x290`) is preferable to coming up with wrong names if you aren't sure. -But if you do decide to start naming things, you should check out the ['Naming style' section of the coding guidelines page](coding_guidelines.md#naming-style). +But if you do decide to start naming things, you should check out the ['Naming style' section of the coding guidelines page](/docs/coding_guidelines.md#naming-style).