Update README.md

Author: dimovskidamjan

README.md

@@ -1,30 +1,30 @@
 # App Deploy Script
 
-Deploy script used for creating the tag with tag message in format `internal-all/v1.0.0-1234`, where `internal-all` is marking the workflow that should be started on the CI, `v1.2.3` represents app version and `1234` represents the build number. Tag message set from this script can be used later for the changelog message on any CI (e.g. Bitrise). The build number is number calculated as a total number of tags available on GitHub incremented by one.
+Deploy script used for creating tags with a tag message in the format `internal-all/v1.0.0-1234`, where `internal-all` is marking the workflow that should be started on the CI, `v1.2.3` represents app version and `1234` represents the build number. Tag message set from this script can be used later for the changelog message on any CI (e.g. Bitrise). The build number is number calculated as the total number of tags available on GitHub incremented by one.
 
 ## Installation
 
-In order to install this script, just run this command in terminal from your <u>project root folder</u>:
+In order to install this script, just run this command in Terminal from your <u>project root folder</u>:
 ```bash
 /bin/bash -c "$(curl -fsSL https://raw.githubusercontent.com/infinum/app-deploy-script/master/install.sh)"
 ```
 
 This script will install `app-deploy` into the `/usr/local/bin/` and `.deploy-options.sh` into the root folder of the project.
-> Note: Do not change name of the `.deploy-options.sh` file!
+> Note: Do not change the name of the `.deploy-options.sh` file!
 
 ## Script modifications
 
 ### Main options
 In general, the script should be used as-is. 
 
-The only part that should be changed is stored inside  `.deploy-options.sh` file under the `deploy_options` function. This part of the script is responsible for creating the first part of the tag that can trigger a specific workflow on CI. If given values are not enough or they are not representing the project structure, they can be replaced with different values. 
+The only part that should be changed is stored inside  `.deploy-options.sh` file under the `deploy_options` function. This part of the script is responsible for creating the first part of the tag that can trigger a specific workflow on CI. If the given values are not enough or they are not representing the project structure, they can be replaced with different values. 
 
-> Keep in mind that prefix `internal-` should be used for the builds created for the internal testing, while builds for beta testing (i.e. Google Play Beta or Apple TestFlight) or public release, should be prefixed as `beta-` or `playstore`/ `appstore`.
+> Keep in mind that the prefix `internal-` should be used for the builds created for the internal testing, while builds for beta testing (i.e. Google Play Beta or Apple TestFlight) or public release, should be prefixed as `beta-` or `playstore`/ `appstore`.
 
 **Final variable name inside `deploy_options` function must stay: `target`** 
 
 ### Configuration flags
-As tag creation is separated into the few small steps, some of them can be skipped and/or disabled by changing configuration flags at the beginning of the script inside `.deploy-options.sh` file.
+As tag creation is separated into a few small steps, some of them can be skipped and/or disabled by changing configuration flags at the beginning of the script inside `.deploy-options.sh` file.
 
 ```bash
 # If enabled, console will be cleared on every script run.
@@ -46,7 +46,7 @@ Script should be run just by calling the script name from the folder where `.dep
 app-deploy
 ```
 
-After that, the script will check if everything is pushed to the remote and if needed it will push all commits before it continues (automatic push can be enabled with `enable_automatic_commit_push` flag). 
+After that, the script will check if everything is pushed to the remote, and if needed it will push all commits before it continues (automatic push can be enabled with `enable_automatic_commit_push` flag). 
 
 ```bash
 ###############################################################
@@ -67,7 +67,7 @@ Targeting commit: e3e45889b
 ---------------------------------------------------------------
 ```
 
-Next step is selecting one or multiple targets that should be run on CI. Enter one or more numbers separated by whitespaces:
+The next step is selecting one or multiple targets that should be run on CI. Enter one or more numbers separated by whitespaces:
 
 ```bash
 
@@ -109,7 +109,7 @@ Getting next build number...
 Next app version is: v2.4.0-6029
 ```
 
-The last step is to add the changelog. When creating the tag, the console will open a preselected text editor where changelog can be added. Keep in mind that closing that editor without entered changelog will result in the script termination.
+The last step is to add the changelog. When creating the tag, the console will open a preselected text editor where a changelog can be added. Keep in mind that closing that editor without entering the changelog will result in a script termination.
 
 ```bash
 ###############################################################
@@ -149,20 +149,27 @@ In the end, the tag is created and pushed to the remote.
 
 ## Updating
 
-Script have the ability to auto-update itself. To update the script, just add `--update` argument.
+The script has the ability to auto-update itself. To update the script, just add `--update` argument.
 ```bash
 app-deploy --update
 ```
 
-Script will fetch latest available changes from the repo and it will change the content of the `app-deploy.sh` script with fetched one. Keep in mind that this will result in overwrite of any changes made by you inside `app-deploy.sh` file. ***This update will not effect `.deploy-options.sh` file.***
+The script will fetch the latest available changes from the repo and it will change the content of the `app-deploy.sh` script with the fetched one. Keep in mind that this will result in overwrite of any changes made by you inside `app-deploy.sh` file. ***This update will not effect `.deploy-options.sh` file.***
 
 ## Contributing
 
 Feedback and code contributions are very much welcome. Just make a pull request with a short description of your changes. By making contributions to this project you permit your code to be used under the same [license](https://github.com/infinum/app-deploy-script/blob/master/LICENSE).
 
 ## Credits
 
-Maintained and sponsored by [Infinum](http://www.infinum.com).
-<a href='https://infinum.com'>
-  <img src='https://infinum.com/infinum.png' href='https://infinum.com' width='264'>
-</a>
+Maintained and sponsored by
+[Infinum](https://infinum.com).
+
+<p align="center">
+  <a href='https://infinum.com'>
+    <picture>
+        <source srcset="https://assets.infinum.com/brand/logo/static/white.svg" media="(prefers-color-scheme: dark)">
+        <img src="https://assets.infinum.com/brand/logo/static/default.svg">
+    </picture>
+  </a>
+</p>