From 6b55fff900a8bd4182f80d2b53370fbe332011a0 Mon Sep 17 00:00:00 2001 From: Mikkel Albrechtsen Date: Tue, 28 May 2024 10:38:22 +0200 Subject: [PATCH] chore(docs): fix typo --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 92c7117..4cbc767 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -15,7 +15,7 @@ For general commits, follow descriptive commit messages that succinctly describe Reference any related issues or pull requests in your commits using appropriate keywords (e.g., "Fix #123"). 4. **Code Style:** Maintain consistent code style and formatting as per the existing project standards. 5. **Testing:** Ensure new code is accompanied by relevant tests where applicable. -6. **Pull Requests:** Submit a pull request against the `develop` branch. Provide a clear description of your changes, ensuring it aligns with the outlined issue or feature request. The title of the PR must be in the fomrat of the [Conventional Commits format](https://www.conventionalcommits.org/en/v1.0.0/). +6. **Pull Requests:** Submit a pull request against the `develop` branch. Provide a clear description of your changes, ensuring it aligns with the outlined issue or feature request. The title of the PR must be in the format of the [Conventional Commits format](https://www.conventionalcommits.org/en/v1.0.0/). ### Versioning Guidelines