From 693ec1a1089d3fb5072159881055444ded40a4a6 Mon Sep 17 00:00:00 2001
From: Ben Schepmans <17271687+bnss@users.noreply.github.com>
Date: Thu, 1 Dec 2022 16:38:00 +0100
Subject: [PATCH] fix: add comma after an introductory clause

---
 content/next/index.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/next/index.md b/content/next/index.md
index 2994854..872a723 100644
--- a/content/next/index.md
+++ b/content/next/index.md
@@ -176,7 +176,7 @@ In a worst case scenario, it's not the end of the world if a commit lands that d
 
 ### Do all my contributors need to use the conventional commit specification?
 
-No! If you use a squash based workflow on Git lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers.
+No! If you use a squash based workflow on Git, lead maintainers can clean up the commit messages as they're merged—adding no workload to casual committers.
 A common workflow for this is to have your git system automatically squash commits from a pull request and present a form for the lead maintainer to enter the proper git commit message for the merge.
 
 ### How does Conventional Commits handle revert commits?