updated

Y-Sindo · Y-Sindo · commit 585acff5f72e · 2024-08-27T13:49:08.000+08:00
diff --git a/articles/azure-signalr/signalr-concept-disaster-recovery.md b/articles/azure-signalr/signalr-concept-disaster-recovery.md
@@ -111,9 +111,8 @@ To enable multiple SignalR Service instances, you should:
         "AzureSignalRServiceTransportType":"Persistent"
     }
     ```
-    >Notes for switching from `Transient` mode to `Persistent` mode on **Azure Functions runtime V3 and above** :
-    >
-    > Under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default on Azure Functions runtime V3 or above. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
+    > [!NOTE]
+    > When switching from `Transient` mode to `Persistent` mode, there may be JSON serialization behavior change, because under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
 
 
 2. Configure multiple SignalR Service endpoints entries in your configuration.
@@ -136,6 +135,7 @@ To enable multiple SignalR Service instances, you should:
     }
     ```
 
+    > [!NOTE]
     > * When you configure Azure SignalR endpoints in the App Service on Azure portal, don't forget to replace `":"` with `"__"`, the double underscore in the keys. For reasons, see [Environment variables](/aspnet/core/fundamentals/configuration#environment-variables).
     >
     > * Connection string configured with the key `{ConnectionStringSetting}` (defaults to "AzureSignalRConnectionString") is also recognized as a primary service endpoint with empty name. But this configuration style is not recommended for multiple endpoints.
diff --git a/articles/azure-signalr/signalr-howto-scale-multi-instances.md b/articles/azure-signalr/signalr-howto-scale-multi-instances.md
@@ -271,9 +271,8 @@ To enable multiple SignalR Service instances, you should:
         "AzureSignalRServiceTransportType":"Persistent"
     }
     ```
-    >Notes for switching from `Transient` mode to `Persistent` mode on **Azure Functions runtime V3 and above** :
-    >
-    > Under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default on Azure Functions runtime V3 or above. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
+    > [!NOTE]
+    > When switching from `Transient` mode to `Persistent` mode, there may be JSON serialization behavior change, because under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
 
 
 2. Configure multiple SignalR Service endpoints entries in your configuration.
@@ -296,6 +295,7 @@ To enable multiple SignalR Service instances, you should:
     }
     ```
 
+    > [!NOTE]
     > * When you configure Azure SignalR endpoints in the App Service on Azure portal, don't forget to replace `":"` with `"__"`, the double underscore in the keys. For reasons, see [Environment variables](/aspnet/core/fundamentals/configuration/#environment-variables).
     >
     > * Connection string configured with the key `{ConnectionStringSetting}` (defaults to "AzureSignalRConnectionString") is also recognized as a primary service endpoint with empty name. But this configuration style is not recommended for multiple endpoints.

Original file line number	Diff line number	Diff line change
`@@ -111,9 +111,8 @@ To enable multiple SignalR Service instances, you should:`
`111`	`111`	`"AzureSignalRServiceTransportType":"Persistent"`
`112`	`112`	`}`
`113`	`113`	```
`114`		- >Notes for switching from `Transient` mode to `Persistent` mode on Azure Functions runtime V3 and above :
`115`		`- >`
`116`		- > Under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default on Azure Functions runtime V3 or above. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
	`114`	`+ > [!NOTE]`
	`115`	+ > When switching from `Transient` mode to `Persistent` mode, there may be JSON serialization behavior change, because under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
`117`	`116`
`118`	`117`
`119`	`118`	`2. Configure multiple SignalR Service endpoints entries in your configuration.`
`@@ -136,6 +135,7 @@ To enable multiple SignalR Service instances, you should:`
`136`	`135`	`}`
`137`	`136`	```
`138`	`137`
	`138`	`+ > [!NOTE]`
`139`	`139`	> * When you configure Azure SignalR endpoints in the App Service on Azure portal, don't forget to replace `":"` with `"__"`, the double underscore in the keys. For reasons, see [Environment variables](/aspnet/core/fundamentals/configuration#environment-variables).
`140`	`140`	`>`
`141`	`141`	> * Connection string configured with the key `{ConnectionStringSetting}` (defaults to "AzureSignalRConnectionString") is also recognized as a primary service endpoint with empty name. But this configuration style is not recommended for multiple endpoints.
Original file line number	Diff line number	Diff line change
`@@ -271,9 +271,8 @@ To enable multiple SignalR Service instances, you should:`
`271`	`271`	`"AzureSignalRServiceTransportType":"Persistent"`
`272`	`272`	`}`
`273`	`273`	```
`274`		- >Notes for switching from `Transient` mode to `Persistent` mode on Azure Functions runtime V3 and above :
`275`		`- >`
`276`		- > Under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default on Azure Functions runtime V3 or above. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
	`274`	`+ > [!NOTE]`
	`275`	+ > When switching from `Transient` mode to `Persistent` mode, there may be JSON serialization behavior change, because under `Transient` mode, `Newtonsoft.Json` library is used to serialize arguments of hub methods, however, under `Persistent` mode, `System.Text.Json` library is used as default. `System.Text.Json` has some key differences in default behavior with `Newtonsoft.Json`. If you want to use `Newtonsoft.Json` under `Persistent` mode, you can add a configuration item: `"Azure:SignalR:HubProtocol":"NewtonsoftJson"` in `local.settings.json` file or `Azure__SignalR__HubProtocol=NewtonsoftJson` on Azure portal.
`277`	`276`
`278`	`277`
`279`	`278`	`2. Configure multiple SignalR Service endpoints entries in your configuration.`
`@@ -296,6 +295,7 @@ To enable multiple SignalR Service instances, you should:`
`296`	`295`	`}`
`297`	`296`	```
`298`	`297`
	`298`	`+ > [!NOTE]`
`299`	`299`	> * When you configure Azure SignalR endpoints in the App Service on Azure portal, don't forget to replace `":"` with `"__"`, the double underscore in the keys. For reasons, see [Environment variables](/aspnet/core/fundamentals/configuration/#environment-variables).
`300`	`300`	`>`
`301`	`301`	> * Connection string configured with the key `{ConnectionStringSetting}` (defaults to "AzureSignalRConnectionString") is also recognized as a primary service endpoint with empty name. But this configuration style is not recommended for multiple endpoints.