about summary refs log tree commit diff stats
path: root/docs
diff options
context:
space:
mode:
Diffstat (limited to 'docs')
-rw-r--r--docs/README.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/README.md b/docs/README.md
index fb5ff01c..c3a8860f 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -42,7 +42,7 @@ Usage
 

 There are a few environment variables to control the behaviour of Box64.

 

-See [here](USAGE.md) all the environment variables and what they do.

+See [here](USAGE.md) for all the environment variables and what they do.

 

 Note: Box64's Dynarec uses a mechanism with Memory Protection and a SegFault signal handler to handle JIT code. In simpler terms, if you want to use GDB to debug a running program that use JIT'd code (like mono/Unity3D), you will still have many "normal" segfaults triggering. It is suggested to use something like `handle SIGSEGV nostop` in GDB to not stop at each segfault, and maybe put a breakpoint inside `my_memprotectionhandler` in `signals.c` if you want to trap SegFaults.