From 228e64b07d40103d4081a8226d341501fa87e294 Mon Sep 17 00:00:00 2001
From: Georg Teufelberger <55834264+tgeorg-ethz@users.noreply.github.com>
Date: Fri, 3 May 2024 15:58:43 +0200
Subject: [PATCH] fix: Typo in README

---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index bc98c3a..0cb5c0d 100644
--- a/README.md
+++ b/README.md
@@ -56,7 +56,7 @@ jobs:
 ```
 
 ## Description
-By using `tagpr,` the release flow can be made easier and more apparent because it can be put into a flow where the release is completed by pressing the merge button on a pull request that is automatically created.
+By using `tagpr`, the release flow can be made easier and more apparent because it can be put into a flow where the release is completed by pressing the merge button on a pull request that is automatically created.
 
 If there are differences between the last release and the main branch, tagpr generates a pull request for the next release. The tagpr considers a semver tagged commit as a release. It would be standard practice.