change links to 'commercial support' anchor

Signed-off-by: Daniel Holbach <daniel@weave.works>
fluxcd · Dec 12, 2022 · b3436ec · b3436ec
1 parent db68a3d
commit b3436ec
Show file tree

Hide file tree

Showing 5 changed files with 6 additions and 6 deletions.
diff --git a/content/en/blog/2022-10-04-september-update/index.md b/content/en/blog/2022-10-04-september-update/index.md
@@ -105,13 +105,13 @@ We will archive Flux Legacy in November this year. If you still need
 migration help, there are still [free migration
 workshops](https://bit.ly/FluxMigrationSurvey), or reach out for paid
 support to one of the companies [listed
-here](/support/#my-employer-needs-additional-help).
+here](/support/#commercial-support).
 
 Some recent prompts for this include:
 
 - Some of the Flux v1 dependencies are pinned to EOL versions, which
   cannot be upgraded without causing regressions or a cascading
-  amount of changes to the codebase. .
+  amount of changes to the codebase.
 - All Kubernetes dependencies are pinned within version v1.21. That
   version already reached end-of-life support upstream.
 

diff --git a/content/en/blog/2022-11-01-november-update/index.md b/content/en/blog/2022-11-01-november-update/index.md
@@ -114,7 +114,7 @@ Please look into [migrating to Flux v2](/flux/migration/) as soon as possible.
 If you still need migration help, there are still [free migration
 workshops](https://bit.ly/FluxMigrationSurvey), or reach
 out for paid support to one of the companies [listed
-here](/support/#my-employer-needs-additional-help).
+here](/support/#commercial-support).
 
 ### Flux Ecosystem
 

diff --git a/content/en/flux/migration/_index.md b/content/en/flux/migration/_index.md
@@ -14,7 +14,7 @@ We strongly recommend you familiarise yourself with the newest Flux and migrate
 
 If you still need migration help, there are still [free migration
 workshops](https://bit.ly/FluxMigrationSurvey), or reach out for paid
-support to one of the companies [listed here](/support/#my-employer-needs-additional-help).
+support to one of the companies [listed here](/support/#commercial-support).
 
 ## Resources
 

diff --git a/content/en/flux/security/best-practices.md b/content/en/flux/security/best-practices.md
@@ -20,7 +20,7 @@ Some recommendations may overlap with Kubernetes security recommendations, to ke
 this short and more easily maintainable, please refer to [Kubernetes CIS Benchmark](https://www.cisecurity.org/benchmark/kubernetes) for non
 Flux-specific guidance.
 
-For help implementing these recommendations, seek [enterprise support](/support/#my-employer-needs-additional-help).
+For help implementing these recommendations, seek [enterprise support](/support/#commercial-support).
 
 ## Security Best Practices
 

diff --git a/content/en/support.md b/content/en/support.md
@@ -104,7 +104,7 @@ Here are some guidelines about which venue makes the most sense:
 
 Bearing in mind that Issues and [Discussions](https://github.com/fluxcd/flux2/discussions) are more permanent and searchable than Slack conversations, we can avoid unduly expending finite community resources by searching before asking. If you are not exactly sure how to ask your question or otherwise daunted by the idea of permanence, visitors are always welcome in [#flux][] on the [CNCF Slack][].
 
-If your needs are more urgent, more broadly demanding, or more persistent than the best-effort community support resources can provide, you may also consider [a paid support option](#my-employer-needs-additional-help).
+If your needs are more urgent, more broadly demanding, or more persistent than the best-effort community support resources can provide, you may also consider [a paid support option](#commercial-support).
 
 ## Community Help Resources