diff --git a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md
index 93e428a3a54..99bfdce3fb7 100644
--- a/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md
+++ b/content/rancher/v2.5/en/installation/resources/update-ca-cert/_index.md
@@ -113,7 +113,7 @@ Method 3 can be used as a fallback if method 1 and 2 are unfeasible.
 For each cluster under Rancher management (including `local`) run the following command using the Kubeconfig file of the Rancher management cluster (RKE or K3S).
 
 ```
-kubectl patch clusters <REPLACE_WITH_CLUSTERID> -p '{"status":{"agentImage":"dummy"}}' --type merge
+kubectl patch clusters.management.cattle.io <REPLACE_WITH_CLUSTERID> -p '{"status":{"agentImage":"dummy"}}' --type merge
 ```
 
 This command will cause all Agent Kubernetes resources to be reconfigured with the checksum of the new certificate.
@@ -142,4 +142,4 @@ With this method you are recreating the Rancher agents by running a set of comma
 First, generate the agent definitions as described here: https://gist.github.com/superseb/076f20146e012f1d4e289f5bd1bd4971
 
 Then, connect to a controlplane node of the downstream cluster via SSH, create a Kubeconfig and apply the definitions:
-https://gist.github.com/superseb/b14ed3b5535f621ad3d2aa6a4cd6443b
\ No newline at end of file
+https://gist.github.com/superseb/b14ed3b5535f621ad3d2aa6a4cd6443b