From 715318707efab56cf68a3ccf053182d67eea5e72 Mon Sep 17 00:00:00 2001 From: Sergey Elantsev Date: Sun, 3 Mar 2019 13:51:22 +0300 Subject: [PATCH] double-faults misspell fixed (#561) --- blog/content/first-edition/posts/10-double-faults/index.md | 2 +- blog/content/second-edition/posts/07-double-faults/index.md | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/blog/content/first-edition/posts/10-double-faults/index.md b/blog/content/first-edition/posts/10-double-faults/index.md index 3ac4882e..2e13b239 100644 --- a/blog/content/first-edition/posts/10-double-faults/index.md +++ b/blog/content/first-edition/posts/10-double-faults/index.md @@ -196,7 +196,7 @@ struct InterruptStackTable { } ``` -For each exception handler, we can choose an stack from the IST through the `options` field in the corresponding [IDT entry]. For example, we could use the first stack in the IST for our double fault handler. Then the CPU would automatically switch to this stack whenever a double fault occurs. This switch would happen before anything is pushed, so it would prevent the triple fault. +For each exception handler, we can choose a stack from the IST through the `options` field in the corresponding [IDT entry]. For example, we could use the first stack in the IST for our double fault handler. Then the CPU would automatically switch to this stack whenever a double fault occurs. This switch would happen before anything is pushed, so it would prevent the triple fault. [IDT entry]: ./first-edition/posts/09-handling-exceptions/index.md#the-interrupt-descriptor-table diff --git a/blog/content/second-edition/posts/07-double-faults/index.md b/blog/content/second-edition/posts/07-double-faults/index.md index 49938b26..2c6744eb 100644 --- a/blog/content/second-edition/posts/07-double-faults/index.md +++ b/blog/content/second-edition/posts/07-double-faults/index.md @@ -192,7 +192,7 @@ struct InterruptStackTable { } ``` -For each exception handler, we can choose an stack from the IST through the `options` field in the corresponding [IDT entry]. For example, we could use the first stack in the IST for our double fault handler. Then the CPU would automatically switch to this stack whenever a double fault occurs. This switch would happen before anything is pushed, so it would prevent the triple fault. +For each exception handler, we can choose a stack from the IST through the `options` field in the corresponding [IDT entry]. For example, we could use the first stack in the IST for our double fault handler. Then the CPU would automatically switch to this stack whenever a double fault occurs. This switch would happen before anything is pushed, so it would prevent the triple fault. [IDT entry]: ./second-edition/posts/06-cpu-exceptions/index.md#the-interrupt-descriptor-table