From 36de2d43ba702fd5b7e8da3b0f746f622f941a55 Mon Sep 17 00:00:00 2001
From: Giles Gaskell <giles@buildkite.com>
Date: Tue, 3 Sep 2024 13:46:05 +1000
Subject: [PATCH] Fix broken links.

---
 pages/apis/rest_api/rules.md | 4 ++--
 pages/clusters/overview.md   | 2 +-
 2 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/pages/apis/rest_api/rules.md b/pages/apis/rest_api/rules.md
index 9aecd618d1..ba9fe8c07d 100644
--- a/pages/apis/rest_api/rules.md
+++ b/pages/apis/rest_api/rules.md
@@ -4,7 +4,7 @@ The rules API lets you create and manage rules in your organization.
 
 ## Rules
 
-[Rules](/docs/pipelines/rules/overview) allow you to manage permissions between Buildkite resources.
+[Rules](/docs/pipelines/rules) allow you to manage permissions between Buildkite resources.
 
 A rule is used to specify that an action is allowed between a source resource (e.g. a pipeline) and a target resource (e.g. another pipeline). Rules allow you to break out of the defaults provided by Buildkite such as the isolation between [clusters](/docs/clusters/overview).
 
@@ -130,7 +130,7 @@ Required [request body properties](/docs/api#request-body-properties):
 <tbody>
   <tr>
     <th><code>type</code></th>
-    <td>The rule type. Must match one of the [available rule types](/docs/pipelines/rules/overview#available-rule-types)<br>
+    <td>The rule type. Must match one of the [available rule types](/docs/pipelines/rules#available-rule-types)<br>
     <em>Example:</em> <code>"pipeline.trigger_build.pipeline"</code></td>
   </tr>
   <tr>
diff --git a/pages/clusters/overview.md b/pages/clusters/overview.md
index 804f04817f..24e8f89eaf 100644
--- a/pages/clusters/overview.md
+++ b/pages/clusters/overview.md
@@ -33,7 +33,7 @@ You can create as many clusters as your require for your setup.
 Learn more about working with clusters in [Manage clusters](/docs/clusters/manage-clusters).
 
 > 📘 Pipeline triggering
-> Pipelines associated with one cluster cannot trigger pipelines associated with another cluster, unless a [rule](/docs/pipelines/rules/overview) has been created to explicitly allow triggering between pipelines in different clusters.
+> Pipelines associated with one cluster cannot trigger pipelines associated with another cluster, unless a [rule](/docs/pipelines/rules) has been created to explicitly allow triggering between pipelines in different clusters.
 
 ### How should I structure my queues