From 75235f36ede60b8807d8c12f689e54ff853d024c Mon Sep 17 00:00:00 2001
From: Michael Lin <85122413+mwlinca@users.noreply.github.com>
Date: Tue, 1 Oct 2024 13:49:41 -0400
Subject: [PATCH] Update
 k8s-best-practices-spk-integration-via-spk-operator.adoc

---
 .../k8s-best-practices-spk-integration-via-spk-operator.adoc    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/modules/k8s-best-practices-spk-integration-via-spk-operator.adoc b/modules/k8s-best-practices-spk-integration-via-spk-operator.adoc
index 2088352..f638ee3 100644
--- a/modules/k8s-best-practices-spk-integration-via-spk-operator.adoc
+++ b/modules/k8s-best-practices-spk-integration-via-spk-operator.adoc
@@ -1,4 +1,4 @@
-[id="cnf-best-practices-spk-integration-via-spk-operator"]
+[id="k8s-best-practices-spk-integration-via-spk-operator"]
 [id="spk-integration-via-spk-operator"]
 = SPK Integration via SPK Operator
 The SPK runs in a separate namespace from the CNF. The CNF will not have direct permissions to access this namespace. In order to allow applications to manage the lifecycle of the SPK deployment, the SPK operator is used. The SPK Operator defines several CRDs for which CRs are created in the CNF namespace: