Skip to content

Commit 30c2450

Browse files
authored
Update howto-enable-geo-replication.md
Fix Policheck bug https://dev.azure.com/msft-skilling/learn-platform-policheck/_workitems/edit/299154
1 parent 2e3863d commit 30c2450

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-signalr/howto-enable-geo-replication.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ However, managing multiple Azure SignalR Services brings some challenges:
4040
## Harnessing geo-replication
4141
With the new geo-replication feature, Contoso can now establish a replica in Canada Central, effectively overcoming the above-mentioned hurdles.
4242

43-
![Diagram of using one Azure SignalR instance with replica to handle traffic from two countries.](./media/howto-enable-geo-replication/signalr-replica.png "Replica Example")
43+
![Diagram of using one Azure SignalR instance with replica to handle traffic from two countries/regions.](./media/howto-enable-geo-replication/signalr-replica.png "Replica Example")
4444

4545
## Create a SignalR replica
4646
# [Portal](#tab/Portal)
@@ -201,4 +201,4 @@ Replicas inherit most configurations from the primary resource; however, some se
201201
3. **Log Destination Settings**. If not configured on the replicas, only logs from the primary resource will be transferred.
202202
4. **Alerts**.
203203

204-
All other configurations are inherited from the primary resource. For example, access keys, identity, application firewall, custom domains, private endpoints, and access control.
204+
All other configurations are inherited from the primary resource. For example, access keys, identity, application firewall, custom domains, private endpoints, and access control.

0 commit comments

Comments
 (0)