From 0c3565294b594c3d5ae41422dbd090d1426e3031 Mon Sep 17 00:00:00 2001
From: waffle87 <0x6a73@protonmail.com>
Date: Wed, 21 Jun 2023 02:59:48 +0000
Subject: [PATCH] =?UTF-8?q?Deploying=20to=20gh-pages=20from=20@=20qmk/qmk?=
 =?UTF-8?q?=5Ffirmware@2f1cac6e9febd6209ff9a012b7fcd03af4f9cb82=20?=
 =?UTF-8?q?=F0=9F=9A=80?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 coding_conventions_c.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/coding_conventions_c.md b/coding_conventions_c.md
index 3f44da713d4..32f6de7ff75 100644
--- a/coding_conventions_c.md
+++ b/coding_conventions_c.md
@@ -8,8 +8,8 @@ Most of our style is pretty easy to pick up on, but right now it's not entirely
   * Closing Brace: Lined up with the first character of the statement that opens the block
   * Else If: Place the closing brace at the beginning of the line and the next opening brace at the end of the same line.
   * Optional Braces: Always include optional braces.
-    * Good: if (condition) { return false; }
-    * Bad: if (condition) return false;
+    * Good: `if (condition) { return false; }`
+    * Bad: `if (condition) return false;`
 * We encourage use of C style comments: `/* */`
   * Think of them as a story describing the feature
   * Use them liberally to explain why particular decisions were made.