From 131395c3648349833dd4c75a685f16b632fcf9d5 Mon Sep 17 00:00:00 2001
From: Poornima Nayar <poornimakrishnav@gmail.com>
Date: Tue, 30 Apr 2024 22:34:42 +0100
Subject: [PATCH] Fix typo on SignalR Scale Multi Instances

---
 articles/azure-signalr/signalr-howto-scale-multi-instances.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/articles/azure-signalr/signalr-howto-scale-multi-instances.md b/articles/azure-signalr/signalr-howto-scale-multi-instances.md
index 55e257cb0269c..efa80af478b98 100644
--- a/articles/azure-signalr/signalr-howto-scale-multi-instances.md
+++ b/articles/azure-signalr/signalr-howto-scale-multi-instances.md
@@ -31,7 +31,7 @@ dotnet user-secrets set Azure:SignalR:ConnectionString:backup:secondary <Connect
 
 ### Add multiple endpoints from code
 
-A `ServicEndpoint` class describes the properties of an Azure SignalR Service endpoint.
+A `ServiceEndpoint` class describes the properties of an Azure SignalR Service endpoint.
 You can configure multiple instance endpoints when using Azure SignalR Service SDK through:
 ```cs
 services.AddSignalR()
@@ -274,4 +274,4 @@ When no `primary` endpoint is available, the client's `/negotiate` picks from th
 You can use multiple endpoints in high availability and disaster recovery scenarios.
 
 > [!div class="nextstepaction"]
-> [Setup SignalR Service for disaster recovery and high availability](./signalr-concept-disaster-recovery.md)
\ No newline at end of file
+> [Setup SignalR Service for disaster recovery and high availability](./signalr-concept-disaster-recovery.md)