aboutsummaryrefslogtreecommitdiff
path: root/book
diff options
context:
space:
mode:
authorJorge Aparicio <jorge@japaric.io>2019-08-21 10:28:07 +0200
committerJorge Aparicio <jorge@japaric.io>2019-08-21 10:28:07 +0200
commit009ca9a0be6e6a95be872ff1e20ca79223df63da (patch)
tree3982690020b1b8f4e37a0fc8a618f361f5620d97 /book
parent07b2b4d83078d0fd260d5f0812e8d5a34d02b793 (diff)
fix link
Diffstat (limited to 'book')
-rw-r--r--book/en/src/internals/critical-sections.md2
1 files changed, 1 insertions, 1 deletions
diff --git a/book/en/src/internals/critical-sections.md b/book/en/src/internals/critical-sections.md
index 8bad6cb..046098e 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.