From 5c9335a4e4c6d21e5529bd44f9ca2e3776204e81 Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 3 Oct 2025 09:57:49 +0000
Subject: [PATCH 1/2] Initial plan


From f91f6f90e653a07067acbe2ab37986e42a8f9f7c Mon Sep 17 00:00:00 2001
From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com>
Date: Fri, 3 Oct 2025 10:04:04 +0000
Subject: [PATCH 2/2] Add documentation for HIGHLIGHT regions in README

Co-authored-by: BenjaminMichaelis <22186029+BenjaminMichaelis@users.noreply.github.com>
---
 README.md | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/README.md b/README.md
index 62644e27e..91ef5b217 100644
--- a/README.md
+++ b/README.md
@@ -77,6 +77,8 @@ When you see matching `#region INCLUDE` and `#endregion INCLUDE` tags in a listi
 
 When there are matching `#region EXCLUDE` and `#endregion EXCLUDE` tags in a listing, even if these are within two `INCLUDE` tags, this section is omitted from being visible in the book and replaced with a `// ...` just to try and bring more clarity to the point that is actually being taught in that listing.
 
+When you see matching `#region HIGHLIGHT` and `#endregion HIGHLIGHT` tags within an `INCLUDE` region, this indicates that the particular code section is emphasized in the book, typically with special formatting or shading to draw attention to the key concept being demonstrated.
+
 In addition, any line that ends with a `// EXCLUDE` is a line that is omitted from being seen in the book.
 
 ## Questions/Bugs