fix(docs): fix-links (#33121)

**Description**
<!--
Please include a summary of the change and which issue is fixed. Please
also include relevant motivation and context. List any dependencies that
are required for this change.
-->
⚒️ Fixes  # <!--(issue)-->

**⚙️ Type of change**

- [ ] ⚙️ Feature/App addition
- [ ] 🪛 Bugfix
- [ ] ⚠️ Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] 🔃 Refactor of current code
- [x] 📜 Documentation Changes

**🧪 How Has This Been Tested?**
<!--
Please describe the tests that you ran to verify your changes. Provide
instructions so we can reproduce. Please also list any relevant details
for your test configuration
-->

**📃 Notes:**
<!-- Please enter any other relevant information here -->

**✔️ Checklist:**

- [ ] ⚖️ My code follows the style guidelines of this project
- [ ] 👀 I have performed a self-review of my own code
- [ ] #️⃣ I have commented my code, particularly in hard-to-understand
areas
- [x] 📄 I have made changes to the documentation
- [ ] 🧪 I have added tests to this description that prove my fix is
effective or that my feature works
- [ ] ⬆️ I increased versions for any altered app according to semantic
versioning
- [ ] I made sure the title starts with `feat(chart-name):`,
`fix(chart-name):`, `chore(chart-name):`, `docs(chart-name):` or
`fix(docs):`

**➕ App addition**

If this PR is an app addition please make sure you have done the
following.

- [ ] 🖼️ I have added an icon in the Chart's root directory called
`icon.png`

---

_Please don't blindly check all the boxes. Read them and only check
those that apply.
Those checkboxes are there for the reviewer to see what is this all
about and
the status of this PR with a quick glance._

website/src/content/docs/general/support-policy.md

@@ -35,7 +35,7 @@ We also offer free support via a support-ticketing system on Discord, according
 - We offer support for all ClusterTool functions, except those under `adv` and `charts`
 - If you deviate from default configurations significantly, we cannot guarantee a bootstrap will work and support will be limited on a case-by-case basis.
 - We do provide support for issues regarding talconfig.yaml, as long as ClusterTool is used for the deployment.
-- We do provide *basic* assistance with [Talos OS](../guides/talos/), when deployed or maintained through ClusterTool (upgrades, config changes etc)
+- We do provide *basic* assistance with [Talos OS](/guides/talos/), when deployed or maintained through ClusterTool (upgrades, config changes etc)
 - We do provide support for FluxCD setup and layout, as long as ClusterTool is used for the deployment.
 - We *only* provide support for the latest version of ClusterTool. Please ensure you are utilizing the latest version before requesting support.
 
@@ -47,7 +47,7 @@ We also offer free support via a support-ticketing system on Discord, according
 ## Helm Chart Support Policy
 
 - We offer support for all features available in our helm-charts, including all options in the common-chart.
-- We offer [basic documentation](../guides/helm/) and support for installing, upgrading and editing our Helm-Charts using Helm.
+- We offer [basic documentation](/guides/) and support for installing, upgrading and editing our Helm-Charts using Helm.
 - We do not support external secret management outside of values.yaml
 - We offer support for all our charts trains, except `incubator`, `dev`, and `test`.
 - We cannot guarantee special characters will work flawlessly in any field.
@@ -61,7 +61,7 @@ Some [(common-chart)](../common/) features might not work correctly with all cha
 ## FluxCD Support Policy
 
 - We offer support for our Helm-Charts values in FluxCD as outlined in Helm Chart Support.
-- We offer [basic documentation](../guides/fluxcd/) and support on how to create a `helm-release` file, to deploy our helm-charts on Flux.
+- We offer [basic documentation](/guides/fluxcd/) and support on how to create a `helm-release` file, to deploy our helm-charts on Flux.
 - To be eligible for FluxCD support your repository must be public.
 - All information being provided *must* be un-encrypted. You can obfuscate any sensitive information as needed.