From fb711a429aa5d67d1330ea91e9af4a17f5d0733b Mon Sep 17 00:00:00 2001
From: theboringstuff <39027092+theboringstuff@users.noreply.github.com>
Date: Thu, 7 Nov 2024 17:26:37 +0300
Subject: [PATCH] fix

---
 documentation/internal/Release.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/documentation/internal/Release.md b/documentation/internal/Release.md
index bca471e79..076f240a0 100644
--- a/documentation/internal/Release.md
+++ b/documentation/internal/Release.md
@@ -1,13 +1,13 @@
 # Releasing KubeMarine
 
 If you want to make a new KubeMarine release, you need to do following:
-1. Update KubeMarine version and create tag (replace `X.X.X` with actual version):
+1. On the target git branch, update KubeMarine version and create tag (replace `X.X.X` with actual version):
     ```
     python3 -m pip install bumpver
     python3 -m bumpver update --set-version=X.X.X
     ```
-2. Create a new pre-release for your tag. Do not forget to generate release notes.
-3. Wait for GitHub Actions completion and verify released artifacts. Following artifacts are essential for each release:
+2. Create a new pre-release for your tag on [GitHub Release page](https://github.com/Netcracker/KubeMarine/releases). Do not forget to generate release notes.
+3. Wait for [GitHub Actions](https://github.com/Netcracker/KubeMarine/actions) completion and verify released artifacts. Following artifacts are essential for each release:
     * KubeMarine binaries for different OS. They could be found in release assets.
     * KubeMarine python distribution package. It could be found in release assets.
     * [KubeMarine image](https://github.com/Netcracker/KubeMarine/pkgs/container/kubemarine).