Update signalr-howto-scale-multi-instances.md

vicancy · web-flow · commit 71eb4b436c1a · 2024-11-29T11:08:14.000+08:00
diff --git a/articles/azure-signalr/signalr-howto-scale-multi-instances.md b/articles/azure-signalr/signalr-howto-scale-multi-instances.md
@@ -122,7 +122,7 @@ services.AddSignalR()
             });
 ```
 
-`ServiceOptions.Endpoints` also supports hot-reload. You could configure `ServiceOptions` using [options pattern](/aspnet/core/fundamentals/configuration/options?#ioptionsmonitor) to hot-reload the endpoints from your configurations and customize how they are loaded. The below sample code shows how to load connection strings from one configuration section and public URL exposed by [reverse proxies](./signalr-howto-reverse-proxy-overview.md) from another:
+`ServiceOptions.Endpoints` also supports hot-reload. The below sample code shows how to load connection strings from one configuration section and public URL exposed by [reverse proxies](./signalr-howto-reverse-proxy-overview.md) from another, and as long as configuration supports hot-reload, the endpoints could be updated on the fly.
 ```cs
 services.Configure<ServiceOptions>(o =>
 {

Original file line number	Diff line number	Diff line change
`@@ -122,7 +122,7 @@ services.AddSignalR()`
`122`	`122`	`});`
`123`	`123`	```
`124`	`124`
`125`		-`ServiceOptions.Endpoints` also supports hot-reload. You could configure `ServiceOptions` using [options pattern](/aspnet/core/fundamentals/configuration/options?#ioptionsmonitor) to hot-reload the endpoints from your configurations and customize how they are loaded. The below sample code shows how to load connection strings from one configuration section and public URL exposed by [reverse proxies](./signalr-howto-reverse-proxy-overview.md) from another:
	`125`	+`ServiceOptions.Endpoints` also supports hot-reload. The below sample code shows how to load connection strings from one configuration section and public URL exposed by [reverse proxies](./signalr-howto-reverse-proxy-overview.md) from another, and as long as configuration supports hot-reload, the endpoints could be updated on the fly.
`126`	`126`	```cs
`127`	`127`	`services.Configure<ServiceOptions>(o =>`
`128`	`128`	`{`