From d53d85ad46a115ba871c6da8273a242e790c810c Mon Sep 17 00:00:00 2001
From: Matthew Richards <32678030+MRichards99@users.noreply.github.com>
Date: Tue, 2 Nov 2021 12:16:19 +0000
Subject: [PATCH] docs: follow Angular commit message capitalisation #242

Co-authored-by: Viktor Bozhinov <45173816+VKTB@users.noreply.github.com>
---
 README.md | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/README.md b/README.md
index 5732e930..8e92e41c 100644
--- a/README.md
+++ b/README.md
@@ -305,21 +305,21 @@ standard:
 
 ```
 # Commit to edit a CI job
-ci: Edit linting job #issue-number
+ci: edit linting job #issue-number
 
 # Commit for a bug fix
-fix: Fix bug found with count endpoints #issue-number
+fix: fix bug found with count endpoints #issue-number
 
 # Commit for a new feature
-feat: Add endpoints for search API #issue-number
+feat: add endpoints for search API #issue-number
 
 # Commit which introduces a breaking change for users
-BREAKING CHANGE: Change format of `config.json`, the previous version is no longer supported #issue-number
+BREAKING CHANGE: change format of `config.json`, the previous version is no longer supported #issue-number
 
 # You can also use `BREAKING CHANGE:` in the additional information if the commit also adds a new feature, like so:
-feat: My new feature #issue-number
+feat: my new feature #issue-number
 
-BREAKING CHANGE: This feature means X functionality has been removed
+BREAKING CHANGE: this feature means X functionality has been removed
 ```
 
 For each pull request, only one commit message in this format is required to satisfy the