diff --git a/.github/workflows/lint_PR.yml b/.github/workflows/lint_PR.yml
index 6b1a667..22e5d7c 100644
--- a/.github/workflows/lint_PR.yml
+++ b/.github/workflows/lint_PR.yml
@@ -10,14 +10,15 @@ jobs:
        uses: NejcZdovc/comment-pr@v1
        with: 
          message: |
-         
+
                 **Conventional commits**
 
-                Our repositories follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification. Releasing to GitHub and NPM is done with the support of [semantic-release](https://semantic-release.gitbook.io/semantic-release/).
 
-                Pull requests should have a title that follows the specification, otherwise, merging is blocked. If you are not familiar with the specification simply ask maintainers to modify. You can also use this cheatsheet if you want:
+       Our repositories follow [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/#summary) specification. Releasing to GitHub and NPM is done with the support of [semantic-release](https://semantic-release.gitbook.io/semantic-release/).
+
+       Pull requests should have a title that follows the specification, otherwise, merging is blocked. If you are not familiar with the specification simply ask maintainers to modify. You can also use this cheatsheet if you want:
 
-                - `fix: ` prefix in the title indicates that PR is a bug fix and PATCH release must be triggered.
+       - `fix: ` prefix in the title indicates that PR is a bug fix and PATCH release must be triggered.
                 - `feat: ` prefix in the title indicates that PR is a feature and MINOR release must be triggered.
                 - `docs: ` prefix in the title indicates that PR is only related to the documentation and there is no need to trigger release.
                 - `chore: ` prefix in the title indicates that PR is only related to cleanup in the project and there is no need to trigger release.