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

---
 documentation/internal/Release.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/internal/Release.md b/documentation/internal/Release.md
index 278886ac2..bca471e79 100644
--- a/documentation/internal/Release.md
+++ b/documentation/internal/Release.md
@@ -7,7 +7,7 @@ If you want to make a new KubeMarine release, you need to do following:
     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 tag:
+3. Wait for GitHub 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).