From 435a6284d562b9389f5d1945a55d423538ed1acf Mon Sep 17 00:00:00 2001
From: "Grot (@grafanabot)" <43478413+grafanabot@users.noreply.github.com>
Date: Wed, 21 Jun 2023 03:10:09 -0400
Subject: [PATCH] [v10.0.x] Docs: fix broken upgrade link to alerting (#70416)

Docs: fix broken upgrade link to alerting (#70415)

(cherry picked from commit 45fe250f3e0c470b194a02e70dc6f7b2ee43e568)

Co-authored-by: brendamuir <100768211+brendamuir@users.noreply.github.com>
---
 docs/sources/breaking-changes/breaking-changes-v10-0.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/sources/breaking-changes/breaking-changes-v10-0.md b/docs/sources/breaking-changes/breaking-changes-v10-0.md
index eacaec1f058..aeffd1aac67 100644
--- a/docs/sources/breaking-changes/breaking-changes-v10-0.md
+++ b/docs/sources/breaking-changes/breaking-changes-v10-0.md
@@ -76,7 +76,7 @@ Grafana legacy alerting (dashboard alerts) has been deprecated since Grafana v9.
 
 #### Migration path
 
-The new Grafana Alerting was introduced in Grafana 8 and is a superset of legacy alerting. Learn how to migrate your alerts in the [Upgrade Alerting documentation]({{< relref "../alerting/migrating-alerts/" >}}).
+The new Grafana Alerting was introduced in Grafana 8 and is a superset of legacy alerting. Learn how to migrate your alerts in the [Upgrade Alerting documentation]({{< relref "../alerting/set-up/migrating-alerts/" >}}).
 
 ### API keys are migrating to service accounts