From 3b0c286605142438da46e3bbaab585e1d015af65 Mon Sep 17 00:00:00 2001
From: Anton Krivoborodov <63401640+antonkri@users.noreply.github.com>
Date: Thu, 23 Jan 2025 09:57:16 +0100
Subject: [PATCH] docs: update link to contribution request

Issue-ref: closes #136
---
 docs/get_involved.rst | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/get_involved.rst b/docs/get_involved.rst
index c70a8af..ad1d461 100644
--- a/docs/get_involved.rst
+++ b/docs/get_involved.rst
@@ -53,7 +53,7 @@ and a `rigid software development process <https://eclipse-score.github.io/score
 
 Contributions to the SCORE project must therefore follow the technical direction of the project and the SCORE 
 architecture. All work in SCORE will therefore follow a
-`Contribution Request Guideline <https://eclipse-score.github.io/score/process/guidelines/contribution_request/index.html>`_.
+`Contribution Request Guideline <https://eclipse-score.github.io/score/process/guidance/contribution_request/index.html>`_.
 Features on the roadmap of SCORE are defined, Contribution Requests create the basis for individual contributions from
 within the SCORE project and also from the outside.
 
@@ -75,4 +75,4 @@ We value real code based collaboration and will judge new potential contributors
 Active and sustaining contributions are the basis for the ability to shape SCORE.
 
 Making active code contributions via the contribution request process described in the
-`SCORE project handbook <https://eclipse-score.github.io/score/platform_management_plan/project_management.html>`_.
\ No newline at end of file
+`SCORE project handbook <https://eclipse-score.github.io/score/platform_management_plan/project_management.html>`_.