diff --git a/modules/osdk-managing-psa-for-operators-with-escalated-permissions.adoc b/modules/osdk-managing-psa-for-operators-with-escalated-permissions.adoc
index 6663e24b96..8efcd9c6ab 100644
--- a/modules/osdk-managing-psa-for-operators-with-escalated-permissions.adoc
+++ b/modules/osdk-managing-psa-for-operators-with-escalated-permissions.adoc
@@ -3,7 +3,7 @@
 // * operators/operator_sdk/osdk-complying-with-psa.adoc
 
 :_content-type: PROCEDURE
-[id="osdk-managing-psa-for-operators-with-escalated-permissions.adoc_{context}"]
+[id="osdk-managing-psa-for-operators-with-escalated-permissions_{context}"]
 = Managing pod security admission for Operator workloads that require escalated permissions
 
 If your Operator project requires escalated permissions to run, you must edit your Operator's cluster service version (CSV).
diff --git a/operators/operator_sdk/osdk-complying-with-psa.adoc b/operators/operator_sdk/osdk-complying-with-psa.adoc
index 02bfa9ed0a..37239c62ca 100644
--- a/operators/operator_sdk/osdk-complying-with-psa.adoc
+++ b/operators/operator_sdk/osdk-complying-with-psa.adoc
@@ -1,8 +1,9 @@
+
 :_content-type: ASSEMBLY
 [id="osdk-complying-with-psa"]
 = Complying with pod security admission
 include::_attributes/common-attributes.adoc[]
-:context: osdk-complying-with-psa.adoc
+:context: osdk-complying-with-psa
 
 toc::[]