diff --git a/doc/cookbook/generic/Generic.lhs b/doc/cookbook/generic/Generic.lhs
index 0156cd313..24463c207 100644
--- a/doc/cookbook/generic/Generic.lhs
+++ b/doc/cookbook/generic/Generic.lhs
@@ -6,7 +6,7 @@ level.
 
 If a you need nesting because you have different branches in your API tree, you
 might want to jump directly to the [Record-based APIs: the nested records
-case](TODO) cookbook that broaches the subject.
+case](../namedRoutes/NamedRoutes.html) cookbook that broaches the subject.
 
 Shall we begin?
 
diff --git a/doc/cookbook/namedRoutes/NamedRoutes.lhs b/doc/cookbook/namedRoutes/NamedRoutes.lhs
index 8ba007b16..54c552567 100644
--- a/doc/cookbook/namedRoutes/NamedRoutes.lhs
+++ b/doc/cookbook/namedRoutes/NamedRoutes.lhs
@@ -8,7 +8,7 @@ This cookbook explains how to implement such nested-record-based-APIs using
 `NamedRoutes` through the example of a Movie Catalog.
 If you don't need the nested aspect of the record-based API, you might want to look at [Record-based
 APIs: the simple
-case](https://docs.servant.dev/en/stable/cookbook/generic/Generic.html) cookbook
+case](../generic/Generic.html) cookbook
 which covers a simpler implementation in which every endpoint is on the same
 level.
 
@@ -18,7 +18,7 @@ Lastly, we make a Server and a Client out of the API type.
 
 However, it should be understood that this cookbook does _not_ dwell on the
 built-in servant combinators as the [<Structuring APIs> cookbook
-](<https://docs.servant.dev/en/stable/cookbook/structuring-apis/StructuringApis.html>)
+](<../structuring-apis/StructuringApis.html>)
 already covers that angle.
 
 ## Why would I want to use `NamedRoutes` over the alternative `:<|>` operator?
diff --git a/doc/cookbook/structuring-apis/StructuringApis.lhs b/doc/cookbook/structuring-apis/StructuringApis.lhs
index 6924b19cf..a0e603f0a 100644
--- a/doc/cookbook/structuring-apis/StructuringApis.lhs
+++ b/doc/cookbook/structuring-apis/StructuringApis.lhs
@@ -37,7 +37,7 @@ endpoints, just like we turn `a * b + a * c` into
 
 (It should be noted that the `(:<|>)` operator is not the only way of combining
 endpoints with Servant. Other techniques are shown in subsequent cookbooks. See
-record-based design paragraph)
+[record-based alternative for implementing APIs](StructuringApis.html#record-based-alternative-for-implementing-apis))
 
 
 ``` haskell
@@ -215,7 +215,7 @@ It should be noted that the `(:<|>)` is not the only way of combining endpoints.
 Servant offers a convenient way to design APIs with records avoiding the ordering constraint of the operator.
 
 A simple case is approached in the [Record-based APIs: the simple
-case](https://docs.servant.dev/en/stable/cookbook/generic/Generic.html)
+case](../generic/Generic.html)
 cookbook, which deals with flat APIs where every endpoint is on the same level.
 Also, a more complex example with nested record is discussed in [Record-based APIs: the nested
-records case](TODO) in which we implement an API tree with many branches.
+records case](../namedRoutes/NamedRoutes.html) in which we implement an API tree with many branches.