diff --git a/docs/learn/1008-aws-cloudformation.md b/docs/learn/1008-aws-cloudformation.md
index b6106b7f..f93523bd 100644
--- a/docs/learn/1008-aws-cloudformation.md
+++ b/docs/learn/1008-aws-cloudformation.md
@@ -18,7 +18,7 @@ The provisioning strategy detailed below follows S3 best practices. However, to
 
 #### Relays
 
-The first thing to consider when developing a plan based on relays is to read their universe reference: it summarizes the expected inputs and their corresponding formats. [Here](../reference/aws/cloudformation.md) is the Cloudformation one.
+The first thing to consider when developing a plan based on relays is to read their universe reference: it summarizes the expected inputs and their corresponding formats.
 
 ## Initialize a Dagger Project and Environment
 
@@ -64,7 +64,7 @@ Create a file named `template.cue` and add the following configuration to it.
 
 ##### 2. Cloudformation relay
 
-As our plan relies on [Cloudformation's relay](../reference/aws/cloudformation.md), let's dissect the expected inputs by gradually incorporating them into our plan.
+As our plan relies on Cloudformation's relay, let's dissect the expected inputs by gradually incorporating them into our plan.
 
 ```shell
 dagger doc alpha.dagger.io/aws/cloudformation
diff --git a/website/docusaurus.config.js b/website/docusaurus.config.js
index 6720b455..d4091498 100644
--- a/website/docusaurus.config.js
+++ b/website/docusaurus.config.js
@@ -7,7 +7,6 @@ module.exports = {
   tagline: "Dagger is a programmable deployment system",
   url: "https://docs.dagger.io",
   baseUrl: "/",
-  onBrokenLinks: "warn",
   onBrokenMarkdownLinks: "warn",
   favicon: "img/favicon.png",
   organizationName: "Dagger",