diff --git a/modules/images-configuration-registry-mirror-project-secret.adoc b/modules/images-configuration-registry-mirror-project-secret.adoc
index 3e7574c6db3..48210456a61 100644
--- a/modules/images-configuration-registry-mirror-project-secret.adoc
+++ b/modules/images-configuration-registry-mirror-project-secret.adoc
@@ -11,9 +11,6 @@ As a cluster administrator, you can edit the cluster-wide `CRIOCredentialProvide
 
 By default, if your cluster uses an `ImageDigestMirrorSet`, `ImageTagMirrorSet`, or `ImageContentSourcePolicy` object to configure repository mirroring, you must use a global pull secret for mirrored registries. You cannot add an image pull secret to a project. However, you can use the cluster-wide `CRIOCredentialProviderConfig` object to configure the kubelet to trigger the CRI-O credential provider, which enables project-scoped image pull secrets.
 
-:FeatureName: Project-scoped image pull secrets for mirrored registries
-include::snippets/technology-preview.adoc[]
-
 An administrator edits the `CRIOCredentialProviderConfig` object named `cluster`, to list the registries that a developer can pull from by using a project-scoped secret. The administrator then creates an image pull secret in each namespace where it is needed and configures role-based access control (RBAC) permissions that allow the pod's service account within that namespace to access the secret. The admin can create a different pull secret with different credentials for each namespace or use the same pull secret in multiple namespaces. 
 
 When a developer uses a pod spec in one of those namespaces to pull an image from a listed registry, the `CRIOCredentialProviderConfig` object triggers the CRI-O credential provider. The credential provider resolves mirror configurations, discovers namespace-scoped secrets, and generates short-lived authentication files for CRI-O consumption. This process maintains credential isolation between namespaces while preserving existing mirror configuration methods.
@@ -22,7 +19,7 @@ The following is an example `CRIOCredentialProviderConfig` object:
 
 [source,terminal]
 ----
-apiVersion: config.openshift.io/v1alpha1
+apiVersion: config.openshift.io/v1
 kind: CRIOCredentialProviderConfig
 metadata:
   name: cluster
@@ -82,7 +79,6 @@ In this example, the `crio-credential-provider` configuration was generated from
 .Prerequisites
 
 * You have access to the cluster as a user with the `cluster-admin` role.
-* You have enabled the `TechPreviewNoUpgrade` feature set in your cluster's `FeatureGate` custom resource (CR). For more information, see "Understanding feature gates".
 
 // The pull secret step 2 is taken from creating-pull-secret
 .Procedure
@@ -172,7 +168,7 @@ $ oc edit criocredentialproviderconfig cluster
 +
 [source,terminal]
 ----
-apiVersion: config.openshift.io/v1alpha1
+apiVersion: config.openshift.io/v1
 kind: CRIOCredentialProviderConfig
 metadata:
   name: cluster