From 0cdf9a73c6f80c7aff7b4b871a4162aaab4a2f9b Mon Sep 17 00:00:00 2001 From: Sven van Heugten Date: Fri, 13 Mar 2026 06:14:03 +0100 Subject: [PATCH] Fix typos in README --- README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/README.md b/README.md index b3d4095..51d6250 100644 --- a/README.md +++ b/README.md @@ -1,8 +1,8 @@ # git-check-assertions -I recently wrote two blogs posts arguing that there might be some value in writing verifiable claims, i.e. assertions, inside of our commit messages: +I recently wrote two blog posts arguing that there might be some value in writing verifiable claims, i.e. assertions, inside of our commit messages: -* [Should we start writing verifiable claims in commit message?](https://sven.memcmp.org/2026-02-19-should-we-start-writing-verifiable-claims-in-commit-messages/) +* [Should we start writing verifiable claims in commit messages?](https://sven.memcmp.org/2026-02-19-should-we-start-writing-verifiable-claims-in-commit-messages/) * [Writing the steps to validate a test in the commit message](https://sven.memcmp.org/2026-02-20-writing-the-steps-to-validate-a-test-in-the-commit-message/) This is a simple verifier for such assertions.