From cab8ab84c5cae97852f9a995c090131a0d56794a Mon Sep 17 00:00:00 2001
From: "mqt-app[bot]" <219534693+mqt-app[bot]@users.noreply.github.com>
Date: Sat, 25 Jul 2026 05:56:43 +0000
Subject: [PATCH] =?UTF-8?q?=F0=9F=93=9D=20Update=20templated=20files?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 docs/contributing.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/contributing.md b/docs/contributing.md
index ee1b38bf3..b6acd3ae6 100644
--- a/docs/contributing.md
+++ b/docs/contributing.md
@@ -597,7 +597,7 @@ The docs can then be found in the {code}`docs/_build` directory.
 If something goes wrong, the CI pipeline will notify you. Here are some tips for
 finding the cause of certain failures:
 
-- If any of the {code}`CI / 🇨‌ Test` checks fail, this indicates build errors or
+- If any of the {code}`CI / 🇨 Test` checks fail, this indicates build errors or
   test failures in the C++ part of the code base. Look through the respective
   logs on GitHub for any error or failure messages.
 
@@ -614,7 +614,7 @@ finding the cause of certain failures:
   been raised by {code}`clang-tidy` when checking the C++ part of your changes
   for warnings or style guideline violations. The individual messages frequently
   provide helpful suggestions on how to fix the warnings. If you don't see any
-  messages, but the {code}`🇨‌ Lint / 🚨 Lint` check is red, click on the
+  messages, but the {code}`🇨 Lint / 🚨 Lint` check is red, click on the
   {code}`Details` link to see the full log of the check and a step summary.
 
 - If the {code}`pre-commit.ci` check fails, some of the {code}`prek` checks