Update deployment steps

Signed-off-by: Georgi Michev <georgi.michev@vereign.com>

Chart.yaml

 apiVersion: v1
-appVersion: v1.1.2
+appVersion: v1.1.3
 description: task deployment
 name: task
-version: 1.1.2
+version: 1.1.3
 icon: "https://www.vereign.com/wp-content/themes/vereign2020/images/vereign-logo.svg"

README.md

@@ -10,10 +10,11 @@ The pipeline in this repo builds image from the source code repo in eclipse as a
 
 When changes to helm or the app are made and deployment is needed, execute the following steps:
 1. Clone the repo and start working on a new branch.
-2. Execute `git submode update --remote --recursive -init` to update source to latest commit on eclipse main branch.
+1. Execute `git submodule update --remote --recursive --init` to update source to latest commit on eclipse main branch.
 1. Edit `Chart.yaml` with the new chart version (example: 1.4.3) and app version it's intended to use (example: v1.4.3).
-2. Create a new tag with the intended app version (v1.4.3)
-3. Wait for pipelines to finish and manually trigger deployment to either `dev-ssi` or `prod-ssi(vault)` clusters.
+1. Create merge request from the update branch.
+1. Create a new tag from main branch with the intended app version (v1.4.3)
+1. Wait for pipelines to finish and manually trigger deployment to either `dev-ssi` or `prod-ssi(vault)` clusters.
 
 ## Values