From b1dcb396627cbe02971d86a90e544c1246f38a3a Mon Sep 17 00:00:00 2001
From: himanshi1505 <bhandari.himanshi15@gmail.com>
Date: Sat, 25 Apr 2026 00:09:28 +0530
Subject: [PATCH] docs(p15-initproc): add missing question mark

---
 p15-initproc.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/p15-initproc.md b/p15-initproc.md
index 66d35ce..625ec57 100644
--- a/p15-initproc.md
+++ b/p15-initproc.md
@@ -57,7 +57,7 @@ its code segment selector base set as `STARTPROC`.
 
 Virtualizing memory only partly solves the isolation problem. What stops a
 process from calling instructions like `lgdt` and `lidt` to take control of the
-memory segments and the interrupts. If a process wants to illegally overwrite OS
+memory segments and the interrupts? If a process wants to illegally overwrite OS
 code, it can setup its own GDT by calling `lgdt` like in `seginit` in `vm.c` to
 give itself permission to access other parts of memory.