Skip to content

Commit ee29d84

Browse files
authored
Update server-graceful-shutdown.md
1 parent f26c25f commit ee29d84

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

articles/azure-signalr/server-graceful-shutdown.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ In general, there will be four stages in a graceful shutdown process:
4444

4545
Azure SignalR Service will try to reroute the client connection on this server to another valid server.
4646

47-
In this scenario, `OnConnectedAsync` and `OnDisconnectedAsync` will be triggered on the new server and the old server respectively with an `IConnectionMigrationFeature` set in the `Context`, which can be used to identify if the client connection was being migrated-in our migrated-out. It could be useful especially for stateful scenarios.
47+
In this scenario, `OnConnectedAsync` and `OnDisconnectedAsync` will be triggered on the new server and the old server respectively with an `IConnectionMigrationFeature` set in the `Context`, which can be used to identify if the client connection was being migrated-in or migrated-out. It could be useful especially for stateful scenarios.
4848

4949
The client connection will be immediately migrated after the current message has been delivered, which means the next message will be routed to the new server.
5050

0 commit comments

Comments
 (0)