From 4f499527fc3a6f26b268bbd89e05980fe610d4d0 Mon Sep 17 00:00:00 2001
From: BlackYps <52536103+BlackYps@users.noreply.github.com>
Date: Sun, 11 Aug 2024 07:40:41 +0200
Subject: [PATCH] Fix links in deployment.md (#6407)

---
 docs/deployment.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/deployment.md b/docs/deployment.md
index 4bba55c91c..584d4d0831 100644
--- a/docs/deployment.md
+++ b/docs/deployment.md
@@ -35,8 +35,8 @@ The last step allows us to systematically post process what we deploy. You can l
 There are three workflows to help with deployment:
 
 - [FAF game type](https://github.com/FAForever/fa/blob/develop/.github/workflows/deploy-faf.yaml)
-- [FAF Beta Balance game type](https://github.com/FAForever/fa/blob/develop/.github/workflows/deploy-faf.yaml)
-- [FAF Develop game type](https://github.com/FAForever/fa/blob/develop/.github/workflows/deploy-faf.yaml)
+- [FAF Beta Balance game type](https://github.com/FAForever/fa/blob/develop/.github/workflows/deploy-fafbeta.yaml)
+- [FAF Develop game type](https://github.com/FAForever/fa/blob/develop/.github/workflows/deploy-fafdevelop.yaml)
 
 The workflows for Beta Balance and Develop trigger periodically. You can review when by evaluating the [cron expression](https://crontab.cronhub.io/). The [API of FAForever](https://github.com/FAForever/faf-java-api/blob/develop/src/main/java/com/faforever/api/deployment/GitHubDeploymentService.java) registers the push to a deployment branch via a webhook. The server creates (and updates) a [deployment status](https://github.com/FAForever/fa/deployments). During that process the server retrieves the game related files, processes it and when everything is fine the new game version will be available in roughly 5 to 10 minutes.