From 009ca9a0be6e6a95be872ff1e20ca79223df63da Mon Sep 17 00:00:00 2001 From: Jorge Aparicio Date: Wed, 21 Aug 2019 10:28:07 +0200 Subject: [PATCH] fix link --- book/en/src/internals/critical-sections.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/en/src/internals/critical-sections.md b/book/en/src/internals/critical-sections.md index 8bad6cb6f2..046098ef51 100644 --- a/book/en/src/internals/critical-sections.md +++ b/book/en/src/internals/critical-sections.md @@ -13,7 +13,7 @@ the task. While a task is within this critical section all the other tasks that may request the resource are *not allowed to start*. How high must the dynamic priority be to ensure mutual exclusion on a particular -resource? The [ceiling analysis](ceiling-analysis.html) is in charge of +resource? The [ceiling analysis](ceilings.html) is in charge of answering that question and will be discussed in the next section. This section will focus on the implementation of the critical section.