From e20a2e0911914a1f6fda470e7ce2ed115b3b9477 Mon Sep 17 00:00:00 2001 From: Jaliya Udagedara Date: Tue, 27 Jun 2017 06:14:07 +0530 Subject: [PATCH] Minor: Typo fix "Communcation" => "Communication" --- .../signalr/overview/getting-started/introduction-to-signalr.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnet/signalr/overview/getting-started/introduction-to-signalr.md b/aspnet/signalr/overview/getting-started/introduction-to-signalr.md index 17248d1c2c..1a373a66d5 100644 --- a/aspnet/signalr/overview/getting-started/introduction-to-signalr.md +++ b/aspnet/signalr/overview/getting-started/introduction-to-signalr.md @@ -131,7 +131,7 @@ The string constants for specifying transports are defined as follows: The SignalR API contains two models for communicating between clients and servers: Persistent Connections and Hubs. -A Connection represents a simple endpoint for sending single-recipient, grouped, or broadcast messages. The Persistent Connection API (represented in .NET code by the PersistentConnection class) gives the developer direct access to the low-level communication protocol that SignalR exposes. Using the Connections communication model will be familiar to developers who have used connection-based APIs such as Windows Communcation Foundation. +A Connection represents a simple endpoint for sending single-recipient, grouped, or broadcast messages. The Persistent Connection API (represented in .NET code by the PersistentConnection class) gives the developer direct access to the low-level communication protocol that SignalR exposes. Using the Connections communication model will be familiar to developers who have used connection-based APIs such as Windows Communication Foundation. A Hub is a more high-level pipeline built upon the Connection API that allows your client and server to call methods on each other directly. SignalR handles the dispatching across machine boundaries as if by magic, allowing clients to call methods on the server as easily as local methods, and vice versa. Using the Hubs communication model will be familiar to developers who have used remote invocation APIs such as .NET Remoting. Using a Hub also allows you to pass strongly typed parameters to methods, enabling model binding.