Merge pull request MicrosoftDocs#16122 from patriksvensson/patch-2

ktoliver · web-flow · commit a97df2f61b7c · 2018-10-03T14:16:57.000-07:00
Corrects typo 'perferred'.
diff --git a/articles/azure-signalr/signalr-overview-scale-aspnet-core.md b/articles/azure-signalr/signalr-overview-scale-aspnet-core.md
@@ -34,7 +34,7 @@ It is still a valid approach to deploy your own Azure web app supporting ASP.NET
 
 One of the key reasons to use the Azure SignalR Service is simplicity. With Azure SignalR Service, you don't need to handle problems like performance, scalability, availability. These issues are handled for you with a 99.9% service-level agreement.
 
-Also, WebSockets are typically the perferred technique to support real-time content updates. However, load balancing a large number of persistent WebSocket connections becomes a complicated problem to solve as you scale. Common solutions leverage: DNS load balancing, hardware load balancers, and software load balancing. Azure SignalR Service handles this problem for you.
+Also, WebSockets are typically the preferred technique to support real-time content updates. However, load balancing a large number of persistent WebSocket connections becomes a complicated problem to solve as you scale. Common solutions leverage: DNS load balancing, hardware load balancers, and software load balancing. Azure SignalR Service handles this problem for you.
 
 Another reason may be you have no requirements to actually host a web application at all. The logic of your web application may leverage [Serverless computing](https://azure.microsoft.com/overview/serverless-computing/). For example, maybe your code is only hosted and executed on demand with [Azure Functions](https://docs.microsoft.com/azure/azure-functions/) triggers. This scenario can be tricky because your code only runs on-demand and doesn't maintain long connections with clients. Azure SignalR Service can handle this situation since the service already manages connections for you. See the [overview on how to use SignalR Service with Azure Functions](signalr-overview-azure-functions.md) for more details. 
 
