From f7caa49eec1c8598c30eaf543c8548adc6a77260 Mon Sep 17 00:00:00 2001
From: Stef Heyenrath <Stef.Heyenrath@gmail.com>
Date: Fri, 12 May 2023 21:58:31 +0200
Subject: [PATCH] Updated Scenarios and States (markdown)

---
 Scenarios-and-States.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Scenarios-and-States.md b/Scenarios-and-States.md
index 1c74b5a..6ec16b9 100644
--- a/Scenarios-and-States.md
+++ b/Scenarios-and-States.md
@@ -5,7 +5,7 @@ WireMock.Net supports _State_ via the notion of _scenarios_. A scenario is essen
 For example, suppose we’re writing a to-do list application consisting of a rich client of some kind talking to a REST service. We want to test that our UI can read the to-do list, add an item and refresh itself, showing the updated list.
 
 Example test code:
-``` c#
+``` csharp
 // Assign
 _server = WireMockServer.Start();