Fix links.

Signed-off-by: Kurt Garloff <kurt@garloff.de>

Author: garloff

blog/2026-01-22-introducing-docs-blog.md

@@ -17,7 +17,7 @@ it was somewhat hard to distill the various aspects and goals of SCS though.
 With the end of the funded project, we split the activities into different organizations
 with distinct goals:
 
-1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/network/) is
+1. The [Forum SCS Standards](https://sovereigncloudstack.org/en/about-scs/) is
    responsible for governing the standardization process. While it pulls significant input
    from the various software projects that belong to the SCS ecosystem, it is neutral towards
    them beyond the preference for standards compliance. This reflects that there can and

community/contribute/adding-docs-guide.md

@@ -10,7 +10,7 @@ Determine the type of your documentation and click to continue.
 2. [Operational documentation](#2-operational-documentation)
 3. [Community documentation](#3-community-documentation)
 
-If unsure don't hestitate to ask us at [Matrix](https://github.com/SovereignCloudStack/docs/blob/main/community/communication/matrix.md)
+If unsure don't hestitate to ask us at [Matrix](https://docs.scs.community/community/tools/matrix)
 
 ## 1. Technical Documentation
 

community/contribute/styleguides/ansible_styleguide.md

@@ -15,7 +15,7 @@ disable the package_latest rule.
 
 ## Key Order
 
-To check the key order we use our own rule. This can be found [here](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/files).
+To check the key order we use our [own rule](https://github.com/osism/zuul-jobs/tree/main/roles/ansible-lint/).
 
 ### Positioning and use of the become directive
 

community/tools/zuul.md

@@ -8,15 +8,17 @@ use Zuul as our main pipeline solution.
 
 ### How to make a repo use Zuul
 
-- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul_deployment)
+Note: This needs to be updated!
+
+- Make Zuul aware of your repository in this [repo](https://github.com/SovereignCloudStack/zuul-scs-jobs)
 - Create a file _.zuul.yaml_
-  - An example can be found [here](https://github.com/SovereignCloudStack/zuul-sandbox/blob/main/.zuul.yaml)
+  - An example can be found [here](https://github.com/SovereignCloudStack/zuul-config/)
   - You can have a job section containing _self-defined_ jobs which you need to write on your own
   - You have to have a project section containing
     - the default-branch name
     - the merge-mode which should be used to auto-merge
     - the jobs to run in each pipeline (gh_check, gh_gate, gh_post, gh_tag)
-    - these pipelines are triggered by events which can be looked up [here](https://github.com/SovereignCloudStack/zuul_config/blob/main/zuul.d/gh_pipelines.yaml)
+    - these pipelines are triggered by events which can be looked up [here](https://github.com/SovereignCloudStack/zuul-config/blob/main/zuul.d/)
     - some default jobs can be found [here](https://opendev.org/zuul/zuul-jobs/src/branch/master/playbooks)
 - If you have _self-defined_ jobs, you need to create a folder _.playbooks_
   - this folder containers ansible playbooks which will be triggered