diff --git a/doc/book/connect/repositories.md b/doc/book/connect/repositories.md
index 1b06385c..eb06e360 100644
--- a/doc/book/connect/repositories.md
+++ b/doc/book/connect/repositories.md
@@ -92,8 +92,8 @@ garage bucket website nix.example.com --allow
 ```
 
 If you need more information about exposing buckets as websites on Garage,
-check [Exposing buckets as websites](/cookbook/exposing_websites.html)
- and [Configuring a reverse proxy](/cookbook/reverse_proxy.html).
+check [Exposing buckets as websites](@/documentation/cookbook/exposing-websites.md)
+ and [Configuring a reverse proxy](@/documentation/cookbook/reverse-proxy.md).
 
 Next, we want to check that our bucket works:
 
diff --git a/doc/book/design/_index.md b/doc/book/design/_index.md
index 93b7a27c..f3a08aaf 100644
--- a/doc/book/design/_index.md
+++ b/doc/book/design/_index.md
@@ -10,11 +10,11 @@ perspective.  It will allow you to understand if Garage is a good fit for
 you, how to better use it, how to contribute to it, what can Garage could
 and could not do, etc.
 
-- **[Goals and use cases](goals.md):** This page explains why Garage was concieved and what practical use cases it targets.
+- **[Goals and use cases](@/documentation/design/goals.md):** This page explains why Garage was concieved and what practical use cases it targets.
 
-- **[Related work](related_work.md):** This pages presents the theoretical background on which Garage is built, and describes other software storage solutions and why they didn't work for us.
+- **[Related work](@/documentation/design/related-work.md):** This pages presents the theoretical background on which Garage is built, and describes other software storage solutions and why they didn't work for us.
 
-- **[Internals](internals.md):** This page enters into more details on how Garage manages data internally.
+- **[Internals](@/documentation/design/internals.md):** This page enters into more details on how Garage manages data internally.
 
 ## Talks