diff --git a/content/en/flux/guides/helmreleases.md b/content/en/flux/guides/helmreleases.md
index da6c1f506..44a3d4083 100644
--- a/content/en/flux/guides/helmreleases.md
+++ b/content/en/flux/guides/helmreleases.md
@@ -382,7 +382,7 @@ spec:
 {{% alert color="info" title="Garbage Collection" %}}
 Stale `ConfigMaps`, previously generated by Kustomize, will be
 removed from the cluster by kustomize-controller if
-[pruning](/flux/components/kustomize/kustomization/#prune) is enabled.
+[pruning](/flux/components/kustomize/kustomizations/#prune) is enabled.
 {{% /alert %}}
 
 ## Refer to values in Secret generated with Kustomize and SOPS
@@ -543,10 +543,10 @@ mongodb False   failed to locate override values file: values-production.yaml
 ## Configure notifications
 
 The default toolkit installation configures the helm-controller to
-broadcast events to the [notification-controller](../components/notification/_index.md).
+broadcast events to the [notification-controller](/flux/components/notification).
 
 To receive the events as notifications, a `Provider` needs to be setup
-first as described in the [notifications guide](notifications.md#define-a-provider).
+first as described in the [notifications guide](/flux/monitoring/alerts/#define-a-provider).
 Once you have set up the `Provider`, create a new `Alert` resource in
 the `flux-system` to start receiving notifications about the Helm
 release: