Update HelmRelease refs to match v2beta2 spec

Signed-off-by: Hidde Beydals <[email protected]>

content/en/flux/installation/configuration/helm-oom-detection.md

@@ -18,7 +18,7 @@ when it reaches a certain threshold (default 95% utilization).
 
 When gracefully shutting down, running Helm actions may mark the release as
 `failed`. Because of this, enabling this feature is best combined with
-thoughtful [remediation strategies](/flux/components/helm/helmreleases/#configuring-failure-remediation).
+thoughtful [remediation strategies](/flux/components/helm/helmreleases/#configuring-failure-handling).
 
 To enable near OOM detection [during bootstrap](boostrap-customization.md) add the following patches to the flux-system `kustomization.yaml`:
 

content/en/flux/security/best-practices.md

@@ -176,7 +176,7 @@ The recommendations below are based on Flux's latest version.
 
     Enforces all reconciliations to impersonate a given Service Account, effectively disabling the use of the privileged service account that would otherwise be used by the controller.
 
-    Tenants must set a service account for each object that is responsible for applying changes to the Cluster (i.e. [HelmRelease](/flux/components/helm/helmreleases/#enforce-impersonation) and [Kustomization](/flux/components/helm/helmreleases/#enforce-impersonation)), otherwise Kubernetes's API Server will not authorize the changes. NB: It is recommended that the default service account used has no permissions set to the control plane.
+    Tenants must set a service account for each object that is responsible for applying changes to the Cluster (i.e. [HelmRelease](/flux/components/helm/helmreleases/#enforcing-impersonation) and [Kustomization](/flux/components/kustomize/kustomizations/#enforcing-impersonation)), otherwise Kubernetes's API Server will not authorize the changes. NB: It is recommended that the default service account used has no permissions set to the control plane.
   </details>
   <details>
     <summary>Audit Procedure</summary>

content/en/flux/use-cases/gh-actions-helm-promotion.md

@@ -196,7 +196,7 @@ spec:
 ```
 
 **Note** that you should adapt the above definitions to match your GitHub repository address.
-If [testing is enabled](https://fluxcd.io/flux/components/helm/helmreleases/#configuring-helm-test-actions)
+If [testing is enabled](https://fluxcd.io/flux/components/helm/helmreleases/#test-configuration)
 in your HelmRelease, you can use the `".*.test.*succeeded.*"`
 expression in the inclusion list instead of `".*.upgrade.*succeeded.*"`.
 This will ensure the promotion happens only after tests have been successfully run.