From 7b38f3713a1eaa5e17d955531d04f535e8b72517 Mon Sep 17 00:00:00 2001
From: Kohei Otsuka <13173186+rjhcnf@users.noreply.github.com>
Date: Tue, 4 Oct 2022 18:52:07 +0200
Subject: [PATCH] Fix typo (#169)

---
 lkmpg.tex | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/lkmpg.tex b/lkmpg.tex
index 530ca74..bb75254 100644
--- a/lkmpg.tex
+++ b/lkmpg.tex
@@ -1803,7 +1803,7 @@ But the job of the kernel is not just to respond to process requests.
 Another job, which is every bit as important, is to speak to the hardware connected to the machine.
 
 There are two types of interaction between the CPU and the rest of the computer's hardware.
-The first type is when the CPU gives orders to the hardware, the order is when the hardware needs to tell the CPU something.
+The first type is when the CPU gives orders to the hardware, the other is when the hardware needs to tell the CPU something.
 The second, called interrupts, is much harder to implement because it has to be dealt with when convenient for the hardware, not the CPU.
 Hardware devices typically have a very small amount of RAM, and if you do not read their information when available, it is lost.