From 557415b0ae1c47c7a53a4ac4df2070280c781a26 Mon Sep 17 00:00:00 2001 From: Craig Brookes Date: Mon, 23 Sep 2024 10:27:52 +0100 Subject: [PATCH] Update doc/user-guides/orphan-dns-records.md Co-authored-by: Michael Nairn --- doc/user-guides/orphan-dns-records.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/doc/user-guides/orphan-dns-records.md b/doc/user-guides/orphan-dns-records.md index 8c654c699..89446d111 100644 --- a/doc/user-guides/orphan-dns-records.md +++ b/doc/user-guides/orphan-dns-records.md @@ -13,7 +13,7 @@ Orphan records can occur when a `DNSRecord` resource (a resource that is created ### How do you spot an orphan record(s) exist? -There is an a prometheus based based alert that we have created that uses some metrics exposed from the DNS components to spot this situation. If you have installed the alerts for Kuadrant under the examples folder, you will see in the alerts tab an alert called `PossibleOrphanedDNSRecords`. When this is firing it means there are likely to be orphaned records in your provider. +There is a prometheus based alert that uses some metrics exposed from the DNS components to spot this situation. If you have installed the alerts for Kuadrant under the examples folder, you will see in the alerts tab an alert called `PossibleOrphanedDNSRecords`. When this is firing it means there are likely to be orphaned records in your provider. ### How do you get rid of an orphan record?