From 008941488452dfe12419f3627291164b8c10e193 Mon Sep 17 00:00:00 2001
From: theboringstuff <39027092+theboringstuff@users.noreply.github.com>
Date: Thu, 7 Nov 2024 16:37:31 +0300
Subject: [PATCH] link

---
 README.md                         | 4 ++++
 documentation/internal/Release.md | 1 -
 2 files changed, 4 insertions(+), 1 deletion(-)

diff --git a/README.md b/README.md
index dc564c00e..f1cc3a580 100644
--- a/README.md
+++ b/README.md
@@ -174,6 +174,10 @@ Also, check out the following inventory examples:
 - [cluster.yaml](examples/cluster.yaml)
 - [procedure.yaml](examples/procedure.yaml)
 
+For maintainers and developers there is useful [internal documentation](/documentation/internal/), for example:
+* [How to write patches](/documentation/internal/Patches.md)
+* [How to make new release](/documentation/internal/Release.md)
+
 ## Issues, Questions
 If you have any problems while working with Kubemarine, feel free to open a [new issue](https://github.com/netcracker/kubemarine/issues) or even
 [PR](https://github.com/netcracker/kubemarine/pulls) with related changes.
diff --git a/documentation/internal/Release.md b/documentation/internal/Release.md
index 93af3a276..278886ac2 100644
--- a/documentation/internal/Release.md
+++ b/documentation/internal/Release.md
@@ -12,5 +12,4 @@ If you want to make a new KubeMarine release, you need to do following:
     * KubeMarine python distribution package. It could be found in release assets.
     * [KubeMarine image](https://github.com/Netcracker/KubeMarine/pkgs/container/kubemarine).
     * [Kubemarine documentation](https://github.com/Netcracker/KubeMarine/tree/main/documentation).
-
 4. Once you have verified that KubeMarine artifacts are OK, change your release from `pre-release` to `latest release` on [GitHub Release page](https://github.com/Netcracker/KubeMarine/releases). This will publish KubeMarine distribution package to PyPI.