added french translation, removed KEYS.md, small contribution and security guideline updates, updates old links

Author: kernelwernel

.github/PULL_REQUEST_TEMPLATE.md

@@ -5,6 +5,7 @@
 ## What does this PR do?
 - [ ] Add a new technique
 - [ ] Add a new feature
+- [ ] Add a new README translation
 - [ ] Improve code
 - [ ] Fix bugs
 - [ ] Refactoring or code organisation

CONTRIBUTING.md

@@ -1,25 +1,46 @@
 # Contribution Guidelines
 
-We have a useful script at `auxiliary/updater.py` that will update:
+
+Make sure to create your PR merge target to the `dev` branch and not the `main` branch. This is because all our prototype code is developed in `dev`, and we usually merge that branch to `main` at least once a week. it keeps our codebase organised and separated between a prototype that we cautiously don't think it's ready to be used by the public yet (especially if it's a new technique being introduced), and an upstream version that we've deemed to be practically ready.
+
+
+Also, please consider adding your name and github in the vmaware.hpp file and the README's credit sections. Your work is valuable to us, and we want to credit you for the improvements you've made. 
+
+
+## Translations
+If you're making translations, please make sure that you actually speak the language, and you have the intention to be as accurate as possible. 
+
+What you SHOULDN'T translate are:
+- text that's in a codeblock
+- text in images
+- text of usernames
+- code
+- and other stuff that should obviously not be translated.
+
+Using translation software like google translate is allowed, but only if you cross-check between the english and translation version to verify if it's done correctly.
+
+The README is quite big, so this is quite an effort. I'm sure you have better thing to do in your life but if you can do this, it would be greatly appreciated :)
+
+
+## Code contributions
+If you're making code changes to the cli or header file, we have a useful script at `auxiliary/updater.py` that will update:
 - the section line numbers in the header banner
 - the date of the update
 - and the library documentation for technique links
 
 It's highly recommended to use this script before sending the PR so that all the above don't have to be manually updated, which can be time consuming and can potentially creep in some human errors. 
 
-Also, make sure to create your PR merge target to the `dev` branch and not the `main` branch. This is because all our prototype code are developed in `dev`. We usually merge that branch to `main` at least once a week, and it keeps our codebase organised and separated between a prototype that we cautiously don't think it's ready to be used by the public yet (especially if it's a new technique being introduced), and an upstream version that we've deemed to be practically ready.
-
-If you have any questions or inquiries, our contact details are in the README.
 
-Lastly, consider adding your name and github in the vmaware.hpp file and the README's credit sections. Your work is valuable to us, and we want to credit you for the improvements you've made. 
-
-# Q&A
-### I want to add a new technique, how would I do that?
+## I want to add a new technique, how would I do that?
 There's a few steps that should be taken:
 1. Make sure to add the technique name in the enums of all the techniques in the appropriate place.
 2. Add the technique function itself in the technique section of the library. Make sure to add it in the right place, as there's preprocessor directives for each platform (Linux, Windows, and Apple)
 3. Add the technique in the technique table situated at the end of the header file. The score should be between 10 and 100. Although there are exceptions, it's advised to follow the aforementioned score range.
 
 
-### I want to make a major change to the library
-Depending on how big the change is, if the change is fairly small then just a simple PR is fine. But if it has hundreds of lines of code changes then it's best to create an issue prior to even starting to write the code, or you can discuss it with us, either works.
+## I want to make a major change to the library
+Depending on how big the change is, if the change is fairly small then just a simple PR is fine. But if it has hundreds of lines of code changes then it's best to create an issue prior to even starting to write the code, or you can discuss it with us, either works.
+
+
+## Notes 
+If you have any questions or inquiries, our contact details are in the README.

KEYS.md

@@ -171,7 +171,7 @@ If you want to learn about the architecture and design of the library, head over
 > 
 > Additionally, software could adjust the behaviour of their program based on the detected environment. It could be useful for debugging and testing purposes, while system administrators could manage configurations differently. Finally, some applications might want to legally restrict usage in VMs as a license clause to prevent unauthorized distribution or testing.
 >
-> There are also projects that utilise our tool such as [Hypervisor-Phantom](https://codeberg.org/Scrut1ny/Hypervisor-Phantom), which is an advanced malware analysis project that we helped strengthen their hypervisor environment and undetectability.
+> There are also projects that utilise our tool such as [Hypervisor-Phantom](https://github.com/Scrut1ny/Hypervisor-Phantom), which is an advanced malware analysis project that we helped strengthen their hypervisor environment and undetectability.
 
 </details>
 

README.md

@@ -158,7 +158,7 @@ endif()
 >
 > 此外，软件可根据检测到的环境调整程序行为。这在调试和测试过程中颇具实用价值，同时系统管理员也能灵活管理配置方案。最后，某些应用程序可能需要通过许可证条款在法律层面限制虚拟机使用，以防止未经授权的分发或测试行为。
 >
-> 还有一些项目采用了我们的工具，例如 [Hypervisor-Phantom](https://codeberg.org/Scrut1ny/Hypervisor-Phantom)，这是一个高级恶意软件分析项目，我们协助其强化了虚拟机监控程序环境并提升了隐蔽性。
+> 还有一些项目采用了我们的工具，例如 [Hypervisor-Phantom](https://github.com/Scrut1ny/Hypervisor-Phantom)，这是一个高级恶意软件分析项目，我们协助其强化了虚拟机监控程序环境并提升了隐蔽性。
 
 </details>