From 65a73aab2b2527ddd0c26a6ca0f99c47eeba52c9 Mon Sep 17 00:00:00 2001
From: Piotr Idzik <65706193+vil02@users.noreply.github.com>
Date: Thu, 18 Apr 2024 00:09:38 +0200
Subject: [PATCH] Denote `override` and `final` as code

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

diff --git a/05-Considering_Maintainability.md b/05-Considering_Maintainability.md
index 2c9a250..b43d561 100644
--- a/05-Considering_Maintainability.md
+++ b/05-Considering_Maintainability.md
@@ -53,6 +53,6 @@ The `assert()` will be removed in release builds which will prevent the `set_val
 So while the second version is uglier, the first version is simply not correct.
 
 
-## Properly Utilize 'override' and 'final'
+## Properly Utilize `override` and `final`
 
 These keywords make it clear to other developers how virtual functions are being utilized, can catch potential errors if the signature of a virtual function changes, and can possibly [hint to the compiler](http://stackoverflow.com/questions/7538820/how-does-the-compiler-benefit-from-cs-new-final-keyword) of optimizations that can be performed.