diff --git a/shared-services/cluster-manifests/README.md b/shared-services/cluster-manifests/README.md
index 752c97e..0724a50 100644
--- a/shared-services/cluster-manifests/README.md
+++ b/shared-services/cluster-manifests/README.md
@@ -21,7 +21,9 @@ Kured is included as a solution to handle occasional required reboots from daily
 
 Typically, your bootstrapping repository wouldn't be a public facing repository like this one, but instead a private GitHub or Azure DevOps repo. The Flux operator deployed with the cluster supports private git repositories as your bootstrapping source. In addition to requiring network line of sight to the repository from your cluster's nodes, you'll also need to ensure that you've provided the necessary credentials. This can come, typically, in the form of certificate based SSH or personal access tokens (PAT), both ideally scoped as read-only to the repo with no additional permissions.
 
-If you are using bicep modify the [`cluster.parameters.json`](../../IaC/bicep/rg-spoke/cluster.parameters.json) file as follows.
+If you are using terraform modify the [`flux.yaml`](../../IaC/terraform/configuration/workloads/flux.tfvars) file.
+
+If you are using bicep modify the [`cluster.parameters.json`](../../IaC/bicep/rg-spoke/cluster.parameters.json) file as follow:
 
 ### Git over SSH