fix: testing if squash merging is the problem

Author: andrejak

docs/CONTRIBUTING.md

@@ -2,7 +2,7 @@
 
 ## Committing to the repository
 
-To be able to publish the correct version to NPM, we are currently following [Angular conventional commit message guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type) which is based on [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). The previous commit message guideline allow us to trigger [semantic-release GitHub action](##client-ci).
+To be able to publish the correct version to NPM, we are currently following [Angular conventional commit message guidelines](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#type) which is based on [conventional commits](https://www.conventionalcommits.org/en/v1.0.0/). The previous commit message guideline allows us to trigger [semantic-release GitHub action](##client-ci).
 
 ### CommitLint to the rescue