diff --git a/docs/help.rst b/docs/help.rst
index fcb1001ed..f068fcaf9 100644
--- a/docs/help.rst
+++ b/docs/help.rst
@@ -254,7 +254,7 @@ CRD issues
 
 .. details:: CustomResourceDefinition.apiextensions.k8s.io "prometheuses.monitoring.coreos.com" is invalid: metadata.annotations: Too long
 
-      This is often a CRD issue which can be fixed by enabling service-side apply option as shown below. Check out `this blog <https://blog.ediri.io/kube-prometheus-stack-and-argocd-25-server-side-apply-to-the-rescue>`_ to learn more. 
+      This is often a CRD issue which can be fixed by enabling server-side apply option as shown below. Check out `this blog <https://blog.ediri.io/kube-prometheus-stack-and-argocd-25-server-side-apply-to-the-rescue>`_ to learn more. 
 
       .. image:: /images/Argocd_crd_issue_fix.png 
       :width: 400
diff --git a/docs/setup-robusta/gitops/argocd.rst b/docs/setup-robusta/gitops/argocd.rst
index 027bc2edc..3b69bc273 100644
--- a/docs/setup-robusta/gitops/argocd.rst
+++ b/docs/setup-robusta/gitops/argocd.rst
@@ -120,7 +120,7 @@ Finally, run ``robusta logs`` from your cli and make sure there is no error.
 
     On some Robusta versions, the sync might fail with ``CustomResourceDefinition.apiextensions.k8s.io “prometheuses.monitoring.coreos.com” is invalid: metadata.annotations: Too long: must have at most 262144 bytes``.
 
-    To solve it, use the workaround proposed :ref:`here <CRD Issues>`.
+    To solve it, use the workaround proposed `here <https://blog.ediri.io/kube-prometheus-stack-and-argocd-25-server-side-apply-to-the-rescue>`_.
 
     
 Configure ArgoCD Declaratively