diff --git a/content/en/blog/2021-08-30-september-update/index.md b/content/en/blog/2021-08-30-september-update/index.md
index f986599fa..3d8786390 100644
--- a/content/en/blog/2021-08-30-september-update/index.md
+++ b/content/en/blog/2021-08-30-september-update/index.md
@@ -201,7 +201,7 @@ section - directly on the home page:
 
 For this we re-use Flux's calendar that is provided by CNCF
 infrastructure, so if you [subscribed to
-it](/community/#subscribing-to-the-flux-dev-calendar)
+it](/community/#subscribing-to-the-flux-calendar)
 in the past, you will continue to receive all the information there.
 
 **🤝 Thanks everyone!** In the last month, 15 people contributed to the
diff --git a/content/en/flux/installation/configuration/multitenancy.md b/content/en/flux/installation/configuration/multitenancy.md
index fa91dcbc8..8a4916f4a 100644
--- a/content/en/flux/installation/configuration/multitenancy.md
+++ b/content/en/flux/installation/configuration/multitenancy.md
@@ -23,8 +23,8 @@ RBAC rules to Flux API objects.
 To give users control over the authorisation, the Flux controllers can _impersonate_ (assume the
 identity of) a service account mentioned in the apply specification (e.g., the field
 `.spec.serviceAccountName` in
-a [`Kustomization` object](https://fluxcd.io/docs/components/kustomize/kustomization/#role-based-access-control)
-or in a [`HelmRelease` object](https://fluxcd.io/docs/components/helm/helmreleases/#role-based-access-control))
+a [`Kustomization` object](https://fluxcd.io/flux/components/kustomize/kustomization/#role-based-access-control)
+or in a [`HelmRelease` object](https://fluxcd.io/flux/components/helm/helmreleases/#role-based-access-control))
 for both accessing resources and applying configuration.
 This lets a user constrain the operations performed by the Flux controllers with RBAC.
 
diff --git a/content/en/roadmap.md b/content/en/roadmap.md
index 319f742d4..66946d727 100644
--- a/content/en/roadmap.md
+++ b/content/en/roadmap.md
@@ -20,7 +20,7 @@ from beta to stable.
 ## Milestones
 
 The GA roadmap has been split into separate milestones.
-The Flux team's current focus is to finalise the tasks from the [Flux GitOps GA](#flux-gitops-ga-q1-2023) milestone.
+The Flux team's current focus is to finalise the tasks from the [Flux GitOps GA](#flux-gitops-ga-completed-in-july-2023) milestone.
 We estimate that the Flux features part of this milestone will become generally available in the first quarter of 2023.
 
 ### Flux GitOps GA (Completed in July 2023)