diff --git a/Scenarios-and-States.md b/Scenarios-and-States.md
index f1a554e..e7eb4fa 100644
--- a/Scenarios-and-States.md
+++ b/Scenarios-and-States.md
@@ -1,6 +1,6 @@
 # Scenarios
 
-WireMock.net supports state via the notion of scenarios. A scenario is essentially a state machine whose states can be arbitrarily assigned. Stub mappings can be configured to match on scenario state, such that stub A can be returned initially, then stub B once the next scenario state has been triggered.
+WireMock.Net supports state via the notion of scenarios. A scenario is essentially a state machine whose states can be arbitrarily assigned. Stub mappings can be configured to match on scenario state, such that stub A can be returned initially, then stub B once the next scenario state has been triggered.
 
 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.