@@ -232,7 +232,7 @@ to the IAM Role.
 
 Trust policies are similar in syntax to permission policies, but for each
 of these two features the trust policy JSON document has particular requirements.
-For EKS Pod Identity, see [here](#for-eks-pod-identity). For OIDC Federation, see
+For EKS Pod Identity, see [here](#with-eks-pod-identity). For OIDC Federation, see
 [here](#supported-identity-types).
 
 To create an IAM Role with a trust policy using ACK, you can use the following custom resource
 
@@ -150,7 +150,7 @@ You may manage these `ConfigMap` and `Secret` resources any way you wish,
 but there are several benefits to managing these with the Flux Kustomize Controller.
 
 It is fairly straightforward to use Kustomize `configMapGenerator`
-to [trigger a Helm release upgrade every time the encoded values change](../guides/helmreleases.md#refer-to-values-in-configmaps-generated-with-kustomize).
+to [trigger a Helm release upgrade every time the encoded values change](../guides/helmreleases.md#reacting-immediately-to-changes-in-referenced-secrets-and-configmaps).
 This common use case currently solveable in Helm
 by [adding specially crafted annotations](https://helm.sh/docs/howto/charts_tips_and_tricks/#automatically-roll-deployments)
 to a chart. The Flux Kustomize Controller method allows you to accomplish this