diff --git a/content/topics/Automation/version-control/advanced-git/naming-git-branches.md b/content/topics/Automation/version-control/advanced-git/naming-git-branches.md
index b6fa1ff1d..af23a9ab8 100644
--- a/content/topics/Automation/version-control/advanced-git/naming-git-branches.md
+++ b/content/topics/Automation/version-control/advanced-git/naming-git-branches.md
@@ -13,7 +13,7 @@ aliases:
 ---
 
 ## Overview
-Apart from having good [Git Branching Strategies](https://tilburgsciencehub.com/topics/collaborate-and-share-your-work/use-github/git-branching-strategies/), it is important to follow some naming conventions to ensure proper maintenance of the repository and a clear, structured way of separating tasks.  To avoid confusions and have an organised overview of every feature that is being worked on, we go through seven best practices for naming branches.
+Apart from having good [Git Branching Strategies](https://tilburgsciencehub.com/topics/automation/version-control/advanced-git/git-branching-strategies/), it is important to follow some naming conventions to ensure proper maintenance of the repository and a clear, structured way of separating tasks.  To avoid confusions and have an organised overview of every feature that is being worked on, we go through seven best practices for naming branches.
 
 ### 1. Use Separators
 When writing a branch name, using separators such as hyphen (-) or slash (/) helps to increase readability of the name. But remember to be consistent with the chosen separator for all branches names.