s/MJIT/RJIT/

1 files changed, 8 insertions, 8 deletions

diff --git a/doc/rjit/rjit.md b/doc/rjit/rjit.md
index 6f19ab3ea7..7f038af88d 100644
--- a/doc/rjit/rjit.md
+++ b/doc/rjit/rjit.md
@@ -1,6 +1,6 @@
-# MJIT
+# RJIT
 
-This document has some tips that might be useful when you work on MJIT.
+This document has some tips that might be useful when you work on RJIT.
 
 ## Supported platforms
 
@@ -11,24 +11,24 @@ The following platforms are either tested on CI or assumed to work.
 
 ### Not supported
 
-The MJIT support for the following platforms is no longer maintained.
+The RJIT support for the following platforms is no longer maintained.
 
 * OS: Windows (mswin, MinGW), Solaris
 * Arch: SPARC, s390x
 
-## Developing MJIT
+## Developing RJIT
 
 ### Bindgen
 
-If you see an "MJIT bindgen" GitHub Actions failure, please commit the `git diff` shown on the failed job.
+If you see an "RJIT bindgen" GitHub Actions failure, please commit the `git diff` shown on the failed job.
 
 For doing the same thing locally, run `make mjit-bindgen` after installing libclang.
 macOS seems to have libclang by default. On Ubuntu, you can install it with `apt install libclang1`.
 
 ### Always run make install
 
-Always run `make install` before running MJIT. It could easily cause a SEGV if you don't.
-MJIT looks for the installed header for security reasons.
+Always run `make install` before running RJIT. It could easily cause a SEGV if you don't.
+RJIT looks for the installed header for security reasons.
 
 ### --mjit-debug vs --mjit-debug=-ggdb3
 
@@ -36,4 +36,4 @@ MJIT looks for the installed header for security reasons.
 which is useful for profiling benchmarks.
 
 `--mjit-debug` alone, on the other hand, disables `-O3` and adds debug flags.
-If you're debugging MJIT, what you need to use is not `--mjit-debug=-ggdb3` but `--mjit-debug`.
+If you're debugging RJIT, what you need to use is not `--mjit-debug=-ggdb3` but `--mjit-debug`.