diff --git a/modules/admission-controller-failure-policy-changing.adoc b/modules/admission-controller-failure-policy-changing.adoc
index eca880ffa891..4a2e92ec3145 100644
--- a/modules/admission-controller-failure-policy-changing.adoc
+++ b/modules/admission-controller-failure-policy-changing.adoc
@@ -8,7 +8,7 @@
 [role="_abstract"]
 You can configure the admission controller failure policy for an existing cluster. This setting determines whether the API server request is allowed (fail open) or blocked (fail closed) if an error or timeout happens in the {product-title-short} validating webhook evaluation. 
 
-. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `admissionControl.failurePolicy` parameter to `Ignore` to fail open, or `Fail` to fail closed.
+. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `spec.admissionControl.failurePolicy` parameter to `Ignore` to fail open, or `Fail` to fail closed.
 . For a cluster that was installed by using Helm, in the `values-public.yaml` file, set the `admissionControl.failurePolicy` value to parameter to `Ignore` to fail open, or `Fail` to fail closed. Then then run the following command:
 +
 [source,terminal]
diff --git a/modules/disable-admission-controller-enforcement.adoc b/modules/disable-admission-controller-enforcement.adoc
index 21dd6bf7aa07..f6a2da36b336 100644
--- a/modules/disable-admission-controller-enforcement.adoc
+++ b/modules/disable-admission-controller-enforcement.adoc
@@ -9,7 +9,7 @@
 You can disable admission controller enforcement on a cluster when installing {product-title-short}. For clusters that you did not install by using the Operator or Helm, you can disable admission controller enforcement from the *Clusters* view on the {product-title} ({product-title-short}) portal. 
 
 .Procedure
-. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `admissionControl.enforcement` parameter to `Disabled`.
+. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `spec.admissionControl.enforcement` parameter to `Disabled`.
 . For a cluster that was installed by using Helm, in the `values-public.yaml` file, set the `admissionControl.enforce` value to `false` and run the following command:
 +
 [source,terminal]
diff --git a/modules/enable-admission-controller-enforcement-existing-cluster.adoc b/modules/enable-admission-controller-enforcement-existing-cluster.adoc
index 6ac0585f7ce2..c49d1672b510 100644
--- a/modules/enable-admission-controller-enforcement-existing-cluster.adoc
+++ b/modules/enable-admission-controller-enforcement-existing-cluster.adoc
@@ -10,7 +10,7 @@ You can view whether admission controller enforcement was enabled on a cluster o
 
 .Procedure
 
-. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `admissionControl.enforcement` parameter to `Enabled`.
+. For a cluster that was installed by using the Operator, in the `SecuredCluster` custom resource (CR), edit the `spec.admissionControl.enforcement` parameter to `Enabled`.
 . For a cluster that was installed by using Helm, in the `values-public.yaml` file, set the `admissionControl.enforce` value to `false` and run the following command:
 +
 [source,terminal]