From 9b429d2effec17dc4e2e7b2dee7a1fd950aa715e Mon Sep 17 00:00:00 2001
From: Amlal El Mahrouss <amlal@nekernel.org>
Date: Sat, 15 Nov 2025 09:29:09 +0100
Subject: feat: kernel: New PE32+ backend, CodeMgr improvements.

Signed-off-by: Amlal El Mahrouss <amlal@nekernel.org>
---
 docs/tex/binary_mutex.tex | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'docs/tex/binary_mutex.tex')

diff --git a/docs/tex/binary_mutex.tex b/docs/tex/binary_mutex.tex
index 1b5a59c2..0f6a6663 100644
--- a/docs/tex/binary_mutex.tex
+++ b/docs/tex/binary_mutex.tex
@@ -12,7 +12,7 @@
 
 \section{Abstract}
 
-{The BinaryMutex is a core component of NeKernel (NeKernel/VMKernel) based systems. The pattern excludes other acquirers to own the USER\_PROCESS that is currently being hold. Thus the acquiree is the USER\_PROCESS itself}
+{The BinaryMutex is a core component of NeKernel (NeKernel/Legacy VMKernel) based systems. The pattern excludes other acquirers to own the USER\_PROCESS that is currently being hold. Thus the acquiree is the USER\_PROCESS itself}
 
 \section{Overview}
 
@@ -64,13 +64,13 @@ class BinaryMutex final {
 \section{Conclusion}
 
 {This design pattern is useful for systems that need to make sure that a process isn't tampered by concurrent usages.
-Thus its existence in VMKernel and NeKernel.}
+Thus its existence in Legacy VMKernel and NeKernel.}
 
 \section{References}
 
 {NeKernel}: \href{https://github.com/nekernel-org/nekernel}{NeKernel}
 
-{VMKernel}: \href{https://snu.systems/specs/vmkernel}{VMKernel}
+{Legacy VMKernel}: \href{https://snu.systems/specs/vmkernel}{Legacy VMKernel}
 
 {BinaryMutex}: \href{https://github.com/nekernel-org/nekernel/blob/dev/dev/kernel/KernelKit/BinaryMutex.h}{BinaryMutex}
 
-- 
cgit v1.2.3

