From ce2e3b169377b8ba6c14fcf25a112fd47260ed9e Mon Sep 17 00:00:00 2001 From: "grafana-delivery-bot[bot]" <132647405+grafana-delivery-bot[bot]@users.noreply.github.com> Date: Tue, 5 Aug 2025 08:14:15 -0500 Subject: [PATCH] [release-12.0.4] Update cloud-migration-assistant.md (#109192) Co-authored-by: Jacob Valdez --- .../administration/migration-guide/cloud-migration-assistant.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/administration/migration-guide/cloud-migration-assistant.md b/docs/sources/administration/migration-guide/cloud-migration-assistant.md index 01d8adc602f..e37a518a0ae 100644 --- a/docs/sources/administration/migration-guide/cloud-migration-assistant.md +++ b/docs/sources/administration/migration-guide/cloud-migration-assistant.md @@ -192,7 +192,7 @@ The migration assistant can migrate the majority of Grafana Alerting resources t - Notification templates {{< admonition type="note">}} -The `grafana-default-email` contact point that's provisioned with every new Grafana instance doesn't have a UID by default and won't be migrated unless you edit or update and save it. You do not need to change the contact point for a UID to be generated when saved. +The `grafana-default-email` contact point that's provisioned with every new Grafana instance doesn't have a UID by default and won't be migrated unless you edit or update and save it. You don't need to change the contact point for a UID to be generated when saved. {{< /admonition >}} This is sufficient to have your Alerting configuration up and running in Grafana Cloud with minimal effort.