diff --git a/satrs-book/book.toml b/satrs-book/book.toml
index 8d01bb6..0fcdc62 100644
--- a/satrs-book/book.toml
+++ b/satrs-book/book.toml
@@ -4,3 +4,5 @@ language = "en"
 multilingual = false
 src = "src"
 title = "The sat-rs book"
+
+[output.linkcheck]
diff --git a/satrs-book/src/communication.md b/satrs-book/src/communication.md
index ba2aa30..bc6cd6f 100644
--- a/satrs-book/src/communication.md
+++ b/satrs-book/src/communication.md
@@ -1,3 +1,5 @@
+<div id="communication-chapter"/>
+
 # Communication with sat-rs based software
 
 Communication is a vital topic for remote system which are usually not (directly)
diff --git a/satrs-book/src/example.md b/satrs-book/src/example.md
index 3a134f2..3d5f057 100644
--- a/satrs-book/src/example.md
+++ b/satrs-book/src/example.md
@@ -39,7 +39,7 @@ The most important components of the TMTC infrastructure include the following c
 - A TM sink sink component which is the target of all sent telemetry and sends it to downlink
    handlers like the UDP and TCP server.
 
-You can read the [Communications chapter](#communication-with-sat-rs-based-software) for more
+You can read the [Communications chapter](./communication.md) for more
 background information on the chose TMTC infrastructure approach.
 
 ### PUS Service Components
@@ -62,8 +62,8 @@ service. This currently includes the following services:
 
 ### Event Management Component
 
-An [event manager]([Event Manager Component](https://docs.rs/satrs-core/0.1.0-alpha.1/satrs_core/event_man/index.html)
-)
+An event manager based on the sat-rs
+[event manager component](https://docs.rs/satrs-core/0.1.0-alpha.1/satrs_core/event_man/index.html)
 is provided to handle the event IPC and FDIR mechanism. The event message are converted to PUS 5
 telemetry by the
 [PUS event dispatcher](https://docs.rs/satrs-core/0.1.0-alpha.1/satrs_core/pus/event_man/alloc_mod/struct.PusEventDispatcher.html).